The ability to embed the LLDB framework within a variety of applications is one of the main design goals for lldb, so this should certainly work. You should look at the Driver.cpp code as a model for how to do this. That code doesn't do anything particularly magical, and does not have the problems you cite...
Are you using debugserver & the gdb-remote process plugin in your code, or the MacOSX Native plugin? The latter has bit-rotted since we've been focusing on the gdb-remote interface. We plan to revive that at some point, but right now using the gdb-remote plugin is the way to go on MacOS X. Jim On Feb 19, 2011, at 9:32 AM, Tomas Nemec wrote: > Hello, > sorry to bother, I am looking for advise on OS X (Mach) debugging and since > there are not many examples I figured this would be the best place to ask. > > I am developing a graphical debugger for OSX - currently it runs as a GDB > frontend. This is very cumbersome and slow though. > I would like to either create my own mini debugger as a backend or possibly > embed lldb. > My mini debugger works but I found out that it is not reliable when trying to > debug a multi-threaded target when more than 1 thread hits a breakpoint. > Trying to single step then sometimes works and sometimes causes the target to > exit... > Could someone give me some pointers or help me if I share my code with you? > (my code is quite small and not difficult to understand) > Also could someone tell me whether it is difficult to embed lldb as a backend > into my Cocoa frontend? Where should I start? > > Many thanks, > Kurt _______________________________________________ > lldb-dev mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev Jim Ingham Apple Developer Tools _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
