[Bug 36013] New: LLDB: StandardStartupTest.TestStopReplyContainsThreadPcs fails on (32-bit) x86

Bug ID 36013
Summary LLDB: StandardStartupTest.TestStopReplyContainsThreadPcs fails on (32-bit) x86
Product lldb
Version 6.0
Hardware PC
OS Linux
Status NEW
Severity normal
Priority P
Component All Bugs
Assignee lldb-dev@lists.llvm.org
Reporter mgorny@gentoo.org
CC llvm-bugs@lists.llvm.org
Blocks 35804

This one seems specific to 32-bit x86 (it fails in my 32-bit chroot, and passes
in 64-bit). I need to check if it's regression though.

FAIL: lldb-Unit ::
tools/lldb-server/tests/./LLDBServerTests/StandardStartupTest.TestStopReplyContainsThreadPcs
(313 of 315)
******************** TEST 'lldb-Unit ::
tools/lldb-server/tests/./LLDBServerTests/StandardStartupTest.TestStopReplyContainsThreadPcs'
FAILED ********************
Note: Google Test filter = StandardStartupTest.TestStopReplyContainsThreadPcs
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from StandardStartupTest
[ RUN      ] StandardStartupTest.TestStopReplyContainsThreadPcs
/var/tmp/portage/dev-util/lldb-6.0.9999/work/lldb-6.0.9999/unittests/tools/lldb-server/tests/ThreadIdsInJstopinfoTest.cpp:47:
Failure
      Expected: stop_reply_pcs[tid]
      Which is: 4160396025
To be equal to: *pc_value
      Which is: 17868764865783398400
Mismatched PC for thread: 25287
[  FAILED  ] StandardStartupTest.TestStopReplyContainsThreadPcs (207 ms)
[----------] 1 test from StandardStartupTest (207 ms total)

Full build & test log attached. This is on release_60 branch with stand-alone
build on Gentoo.

labath@google.com changed bug 36013

Comment # 3 on bug 36013 from labath@google.com

Fixed by r325511 (there was nothing wrong with the debugger, just the test was
not 32bit-compatible).