A few days ago I built lldb 3.3 release on our workstation with redhat enterprise linux 6.3 x86_64 (gcc verison 4.8.2). At the very beginning, lldb seemd to work and I debugged small native programs. Still, the bug showed itself randomly as follows:
- at first, “(lldb)” prompt is missing and input from keyboard is not printed out, which means whatever I type, I can not read them on screen. Still, lldb corresponds to the command I type on condition that I input them correctly. lldb gives tips if I type a wrong command string.
- if situation mentioned above appears and I type “quit” to exit lldb, a segmentation fault (core dumped) happen. I debug lldb with gdb-7.6.1, and track the segmentation fault source to a message “Program received signal SIGSEGV, segmentation fault. 0x3b55c07fc3 in pthread_join () from /lib64/libpthread.so.0”.
Since I am not familiar with multi-thread programming, I can not dig any further. Do you guys have Any clue?