[lldb-dev] What does this piece of hijack code do?
tfiala at google.com
Tue Aug 19 15:26:47 PDT 2014
So if I'm doing this for local Linux llgs-based debugging, I would want to
do the same thing on the PlatformLinux side. Is there any significance to
the name? For example, I'm using this code right now:
ListenerSP listener_sp (new Listener("lldb.*PlatformLinux*.attach.hijack")
On Tue, Aug 19, 2014 at 3:20 PM, Todd Fiala <tfiala at google.com> wrote:
> Ok, thanks.
> On Tue, Aug 19, 2014 at 3:16 PM, Greg Clayton <gclayton at apple.com> wrote:
>> It will get all process events delivered to it (like the initial
>> eStateStopped event) to make sure the attach succeeded. The it will likely
>> re-post the event after unhijacking the process events so LLDB knows about
>> Attach either succeeds or fails immediately (when attaching to a pid or
>> name), or waits when attaching to the next process by name. This can be
>> interrupted by CTRL+C and there is some logic that deals with that.
>> > On Aug 19, 2014, at 3:04 PM, Todd Fiala <tfiala at google.com> wrote:
>> > Hey guys,
>> > In the local MacOSX debugging case when PlatformDarwin::Attach () is
>> eventually called, what is this piece of code really doing?
>> > ListenerSP listener_sp (new
>> > attach_info.SetHijackListener(listener_sp);
>> > process_sp->HijackProcessEvents(listener_sp.get());
>> > What will be that hijacker's responsibility?
>> > Thanks!
>> > --
>> > Todd Fiala | Software Engineer | tfiala at google.com |
> Todd Fiala | Software Engineer | tfiala at google.com | 650-943-3180
Todd Fiala | Software Engineer | tfiala at google.com | 650-943-3180
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev