[llvm-bugs] [Bug 26492] New: TestPrintStackTraces sometimes fails on android arm

via llvm-bugs llvm-bugs at lists.llvm.org
Fri Feb 5 07:06:26 PST 2016


https://llvm.org/bugs/show_bug.cgi?id=26492

            Bug ID: 26492
           Summary: TestPrintStackTraces sometimes fails on android arm
           Product: lldb
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: All Bugs
          Assignee: tberghammer at google.com
          Reporter: labath at google.com
                CC: llvm-bugs at lists.llvm.org
    Classification: Unclassified

Created attachment 15835
  --> https://llvm.org/bugs/attachment.cgi?id=15835&action=edit
Test trace

It seems that the main thread has stopped somewhere in libc, and we cannot
unwind out of it.

Stack trace for thread id=0x4c7e name=a.out queue=None stop reason=none
  frame #0: 0x000000b6e4135c libc.so`None + -18446744073709149347


The address seems to be 0x4cb1c bytes inside the .text section
1454675830.031735000 [9437/97fd]: SectionLoadList::SetSectionLoadAddress
(section = 0x2a40f00
(/home/lldb_build/.lldb/module_cache/remote-android/.cache/208950F0-49F2-74B2-3ABE-0BCAB12FA0BD/libc.so..text),
load_addr = 0x00000000b6df4840) module = 0x2d077e0


Full logs are in the attachment.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20160205/3e7977b9/attachment.html>


More information about the llvm-bugs mailing list