It is the AttachToProcessWithID that hangs and never returns, so I cannot use
my listener yet.
-Philippe
From: jing...@apple.com [jing...@apple.com]
Sent: Wednesday, September 16, 2015 3:34 PM
To: Philippe Lavoie
Cc: lldb-dev@lists.llvm.org
Subject: Re: [l
It is a custom process plug-in using a proprietary protocol to communicate with
the debug target.
In the process plugin's AsyncThread, I set the process private state to
eStateStopped by calling process->SetPrivateState.
Is it enough to broadcast the state change?
The event is in the events lo
A few questions:
Which process plug-in does your debugging target use?
Is it a GDB Remote based debug session?
If so is it using lldb-server?
a custom GDB server?
In general, we expect to receive a eStateStopped process event if the attach is
successful and this is what we are waiting f
Did you try waiting for an event on the listener you've passed to
AttachToProcess? The last event after everything is done should be the
notification to the public listener (i.e. your test_listener) that the process
you attached to has stopped, and nobody is fetching that.
Jim
> On Sep 16, 20
I am trying to attach to a stopped process on our dsp target using the SBTarget
interface but the call hangs.
What I understand is that it is waiting for events on the "lldb.process"
broadcaster using the "lldb.Target.Attach.attach.hijack" listener.
Enabling the logs, I see that the process is
https://llvm.org/bugs/show_bug.cgi?id=24846
Bug ID: 24846
Summary: test runner: multiprocessing test runner sometimes
halting after "hangup"
Product: lldb
Version: unspecified
Hardware: Macintosh
OS: All
https://llvm.org/bugs/show_bug.cgi?id=24843
Bug ID: 24843
Summary: "ninja lldb-server" on OS X reports "error: unknown
target 'lldb-server'"
Product: lldb
Version: unspecified
Hardware: Macintosh
OS: All
https://llvm.org/bugs/show_bug.cgi?id=18832
ema...@freebsd.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=21142
ema...@freebsd.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
