public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Alain Magloire <alain@qnx.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB inferior PID ?
Date: Sun, 15 Jun 2003 02:43:00 -0000	[thread overview]
Message-ID: <3EEBDD4F.30007@redhat.com> (raw)
In-Reply-To: <200305061444.KAA32151@node1.ott.qnx.com>

> Bonjour
> 
> 	Is there a way to get "reliably" the inferior PID ?

Do you want the theory, or the reality :-(

> Scenario, Eclipse/CDT debugger:
> 
> 	I'm using gdb/mi and to separate inferior output from the MI protocol we use 
> gdb --tty=...
> 
> The downside interrupting the inferior is now messy business
> depending on the platfrom.  Totally broken on Solaris, partially
> working on GNU/Linux and windows.
> 
> I've already drop a PR on the solaris platform.
> 
> Solution:
> 
> I'm doing some ugly hack/parsing with
> (gdb) info program
> 
> And retrieving the inferior pid to drop a SIGINT or whatever
> it is call on windows(CTRL-BREAK ?).
> 
> 
> Anyone having something more elegant/reliable?
> 
> Why is the pid(or whatever the host consider to be the "pid") available?
> I undestand that it does not apply to remote/serial debugging.

The theory is that GDB is in async mode and able to accept things like 
an interrupt at any time.  GDB then passes the interrupt down to the 
target - very like GDB already does for remote targets.

You could look at the remote.c code at how it handles interrupts - send 
the interrupt to GDB and then have it dispatch it.

The other is a command to let you do the querying your doing now.

Andrew


      reply	other threads:[~2003-06-15  2:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 14:44 Alain Magloire
2003-06-15  2:43 ` Andrew Cagney [this message]

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=3EEBDD4F.30007@redhat.com \
    --to=ac131313@redhat.com \
    --cc=alain@qnx.com \
    --cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).