From: James Milne <jamesm@filmlight.ltd.uk>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: Interrupting target execution on Linux using GDB/MI
Date: Wed, 01 Apr 2009 16:45:00 -0000 [thread overview]
Message-ID: <5D22D5EE-71AE-46DE-86C0-6A4C58CB0021@filmlight.ltd.uk> (raw)
In-Reply-To: <20090401164152.GD8930@adacore.com>
On 1 Apr 2009, at 17:41, Joel Brobecker wrote:
>> What is the correct procedure when using GDB/MI to interrupt the
>> execution of the inferior process?
>
> There is a GDB/MI command to interrupt the execution of your program.
I attempted to use that, but it does not work when GDB is being used
synchronously. It only works when you are connecting to a gdbserver
and GDB itself is running "asynchronously".
Certainly it doesn't work on OS X when I originally tried it, which
lead me to issuing SIGINT myself.
Regards
James Milne
FilmLight Ltd.
next prev parent reply other threads:[~2009-04-01 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 16:37 James Milne
2009-04-01 16:42 ` Joel Brobecker
2009-04-01 16:45 ` James Milne [this message]
2009-04-01 17:14 ` Marc Khouzam
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=5D22D5EE-71AE-46DE-86C0-6A4C58CB0021@filmlight.ltd.uk \
--to=jamesm@filmlight.ltd.uk \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
/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