[lldb-dev] [Bug 23091] New: Thread info on newly created threads causes segfault
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Tue Mar 31 15:30:41 PDT 2015
https://llvm.org/bugs/show_bug.cgi?id=23091
Bug ID: 23091
Summary: Thread info on newly created threads causes segfault
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: lldb-dev at cs.uiuc.edu
Reporter: chaorenl at google.com
Classification: Unclassified
If the newly created thread is still in libc.so*`__*, a thread info on that
thread will cause immediate segfault.
This could (hopefully) be related to a rare race condition in
TestSetWatchlocation.py, wherein if a breakpoint is hit immediately after
thread creation, the new thread will miss the stop all event, and continue to
be in the running state when the watchpoint is being set, causing a failure.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20150331/d944adfc/attachment.html>
More information about the lldb-dev
mailing list