[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] CDI debugger deadlock issue
|
Check how other stuff is implemented. For example breakpoint setting -
it does stop the target then insert the breakpoint then resume
On Tue, Sep 7, 2010 at 5:52 AM, Mike Wrighton
<mike.wrighton@xxxxxxxxxxxxxx> wrote:
> Hi,
>
> I have a quick question about CDI debugger commands and target
> synchronization. I'm issuing a debugger command from my plug-in as follows:
>
> synchronized (target.getLock()) {
> if (target.isTerminated() || !target.isSuspended()
> || target.isRunning()) {
> return;
> }
> session.postCommand(cmd);
> ...
>
> What seems to be happening is the target itself does not grab the lock when
> it issues it's own commands, so immediately after I've checked that the
> target is suspended, it issues a continue and begins running again, causing
> deadlock when I call postCommand().
>
> Has this been seen before and is there a recommended solution?
>
> Thanks,
> Mike
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
