From: Tudor Popescu <popescu.m.tudor@gmail.com>
To: Jonah Graham <jonah@kichwacoders.com>
Cc: Pedro Alves <palves@redhat.com>, GDB Development <gdb@sourceware.org>
Subject: Re: GDB doesn't interrupt target
Date: Fri, 20 Dec 2019 15:37:00 -0000 [thread overview]
Message-ID: <CAHrp7QCfDKgN_0vhExt0Mb5=bz9ixnHfPOjngnXsYyT0Rd4Vmg@mail.gmail.com> (raw)
In-Reply-To: <CAPmGMvg=rRbsU72avoMbGq5KTOsX8JV1PxYcFD5WwY97JctYfQ@mail.gmail.com>
Hello,
Well we have the following versions:
org.eclipse.cdt 9.3.0.201706122201
org.eclipse.cdt.dsf.gdb 5.3.0.201706122201
org.eclipse.cdt.dsf.gdb.ui 2.6.0.201706122201
On Windows, the suspend works. Should it work on Linux as well?
All the best,
Tudor
On Thu, Dec 19, 2019 at 4:47 PM Jonah Graham <jonah@kichwacoders.com> wrote:
> On Thu, 19 Dec 2019 at 09:22, Pedro Alves <palves@redhat.com> wrote:
>
>> On 12/19/19 1:10 PM, Tudor Popescu wrote:
>> > Indeed the "interrupt" works on Debugger Console, as for the Suspend,
>> the console prints a "^CQuit" just as when killing.
>> This suggests that the suspend button is sending a SIGINT to GDB instead
>> of
>> issing an -exec-interrupt command on the MI channel. (MI's
>> -exec-interrupt
>> command is the equivalent of the "interrupt" command on the console.)
>>
>>
> Thank you Pedro for confirming.
>
> Tudor, where did you get your Eclipse from? If it is a fairly recent and
> unmodified/extended CDT I should be able to reproduce this, but I am going
> to need some more details on exactly how you are using it. Which type of
> launch are you doing for example. If you are using (or writing) a vendor
> extension to CDT it could be that the vendor has overridden the
> implementation of RunControl.suspend() that is in used
> by GDBRunControl_7_12 for GDB >= 7.12.
>
> Please raise a bug
> <https://bugs.eclipse.org/bugs/enter_bug.cgi?product=CDT> in CDT with the
> details and I can look at it further.
>
> Thanks,
> Jonah
>
>
>
next prev parent reply other threads:[~2019-12-20 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 14:20 Tudor Popescu
2019-12-18 14:59 ` Pedro Alves
2019-12-18 15:49 ` Jonah Graham
[not found] ` <CAHrp7QDmyiyyXtpcA_XSN41=eZM3eT3vwhuY5e9WTCqHGD_k1g@mail.gmail.com>
2019-12-19 14:22 ` Pedro Alves
2019-12-19 14:47 ` Jonah Graham
2019-12-20 15:37 ` Tudor Popescu [this message]
2019-12-20 16:23 ` Jonah Graham
2019-12-23 14:37 ` Tudor Popescu
2019-12-23 16:32 ` Jonah Graham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHrp7QCfDKgN_0vhExt0Mb5=bz9ixnHfPOjngnXsYyT0Rd4Vmg@mail.gmail.com' \
--to=popescu.m.tudor@gmail.com \
--cc=gdb@sourceware.org \
--cc=jonah@kichwacoders.com \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox