Re: GDB doesn't interrupt target

Tudor Popescu <[email protected]>
Newsgroups gmane.comp.gdb.devel
Message-ID <CAHrp7QCfDKgN_0vhExt0Mb5=bz9ixnHfPOjngnXsYyT0Rd4Vmg@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 <[email protected]> wrote:

> On Thu, 19 Dec 2019 at 09:22, Pedro Alves <[email protected]> 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
>
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.