No, nothing has changed. lldb only operates in "control other process" mode, not in "observe other process" mode, and controlling yourself is a neat trick you might be able to manage, but would add a lot of complexity for no clear benefit for most of the usages of lldb.
On OSX, you can use CoreSymbolication to take a backtrace of yourself. There are likely similar facilities on other systems. Jim On Mar 4, 2014, at 1:32 PM, Timothee Cour <[email protected]> wrote: > Actually I just realized I've posted a related question before: "process > calling lldb to symbolicate its own backtrace". > However it didn't seem so easy to do judging from the thread. Has anything > changed since then? There should be a simple way to do this important task. > > > On Tue, Mar 4, 2014 at 1:08 PM, Timothee Cour <[email protected]> > wrote: > I'd like to use lldb's backtrace as a library as opposed to using lldb > program, so that I can generate good stack traces inside a C/C++/D program > without having to spawn a separate process that would call 'lldb -p pid'. > > How should I proceed? Or, what is the relevant function call? > > _______________________________________________ > lldb-dev mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
