[Bug general/5620] New: RHEL 5.2 occasional backtraces resolve libc as unknown

["pmuldoon at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

Running testLinuxCoreFileStackTrace(frysk.proc.dead.TestLinuxCore) ...FAIL
  junit.framework.ComparisonFailure: Compare stack traces
expected:<...__libc_start_main ()...> but was:<...[unknown]...>

This can only be replicated via -r 100 (it normally happens deep into the repeat
run). Occasionally, libc_start_main() ends up being resolved as [unknown]. This
does not happen on f8 as far as I can test. 


Time: 0.126
There was 1 failure:
1)
testLinuxCoreFileStackTrace(frysk.proc.dead.TestLinuxCore)junit.framework.ComparisonFailure:
Compare stack traces expected:<...__libc_start_main ()...> but was:<...[unknown]...>
   at frysk.proc.dead.TestLinuxCore.testLinuxCoreFileStackTrace(funit)
   at frysk.junit.Runner.runCases(funit)
   at frysk.junit.Runner.runTestCases(funit)
   at frysk.pkglibdir.funit.main(funit)

-- 
           Summary: RHEL 5.2 occasional backtraces resolve libc as unknown
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: pmuldoon at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=5620

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.