[lldb-dev] a runtime bug for lldb on redhat enterprise linux 6.3 with gcc 4.8.2

[Greg Clayton]

Update your libedit to the latest version. The version that is installed by default is very old. Updating this should fix any prompt issues.

Not sure what is going on with the pthread_join, you will need to debug this or have someone on the linux side help you track this down if it is reproducible.

A _lot_ of fixes have been made on top of tree LLDB, I would recommend actually building the top of tree:

http://lldb.llvm.org/build.html


Greg

On Nov 14, 2013, at 8:27 PM, 杨勇勇 <triple.yang at gmail.com> wrote:

> Hi, all
> 
> 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:
> 1. 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.
> 2. 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?
> 
> Thanks beforehand.
> 
> -- 
> 杨勇勇 (Yang Yong-Yong)
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev