I usually find it best to debug one LLDB using another and step through the Debugger::HandleProcessEvent() and watch as things come out wrong.
> On Jun 19, 2014, at 2:08 PM, Shawn Best <sb...@blueshiftinc.com> wrote: > > Thanks for the pointers Greg and Ed. Lots to chew on. I will get back with > what I find. > > Shawn. > On 6/19/2014 12:18 PM, Ed Maste wrote: >>>> On Jun 19, 2014, at 10:29 AM, Shawn Best <sb...@blueshiftinc.com> wrote: >>>> >>>> Hi All, >>>> >>>> I would like to start contributing to lldb project and help improve it on >>>> linux. I am seeing some strange behaviour that makes lldb appear a little >>>> flakey. Some details of my system: >>>> >>>> - Ubuntu 14.04, 64 bit running inside a VM on windows >>>> - built from top of top of tree with gcc 4.8.2. Issue happens either >>>> configure/make or cmake/ninja >>>> - stock lldb-3.4 version shipped with Ubuntu does not exhibit this >>>> behaviour >>>> >>>> There are two intermittent issues: 1. When I run a program, I see >>>> messages that do not belong (indicating the process was stopped) 2. >>>> There appears to be a race condition sending text to the console where >>>> (lldb) prompt will come out of order making it appear there is no command >>>> prompt. >> Hi Shawn, >> >> There are also some previous threads on this topic in the archives >> that could help give you some background. The discussion was in reply >> to the r202525 commit message. >> >> I described a hacky workaround that works for me in: >> http://lists.cs.uiuc.edu/pipermail/lldb-commits/Week-of-Mon-20140519/011166.html >> >> Can you give it a try? If it "works" for you that will at least >> suggest we share the same issue on FreeBSD and Linux. >> >> -Ed > > _______________________________________________ > lldb-dev mailing list > lldb-dev@cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev _______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
