From: Daniel Jacobowitz <drow@false.org>
To: Bob Rossi <bob_rossi@cox.net>
Cc: PAUL GILLIAM <pgilliam@us.ibm.com>, gdb@sourceware.org
Subject: Re: invoking GDB from FE and signals
Date: Mon, 15 May 2006 21:02:00 -0000 [thread overview]
Message-ID: <20060515202042.GA8673@nevyn.them.org> (raw)
In-Reply-To: <20060515201006.GB21608@brasko.net>
On Mon, May 15, 2006 at 04:10:06PM -0400, Bob Rossi wrote:
> OK, here's the problem. There are 2 case's, using a PTY or not.
>
> I am currently not using a PTY. So, I send the signal via kill. Is this
> correct or incorrect?
I have no idea how to get this right for the pipe case. Maybe someone
else does.
> If I use a PTY, which I'm going to have to reimplement. I'll except
> signals like SIGINT, cause I'll forward them with 'write' to the PTY
> between GDB and CGDB.
I don't think "write" will do it; you need something more complicated.
Maybe I'm wrong and writing the interrupt character will do it.
GDB expects, today, to have a console. It expects C-c to go to the
foreground process group on that console. It arranges to be the
foreground process when GDB is stopped, and for the inferior to be in
the foreground when it is running.
This may not be the most useful behavior for your case.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-15 20:20 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 15:09 Bob Rossi
2006-05-13 15:11 ` Daniel Jacobowitz
2006-05-13 15:19 ` Bob Rossi
2006-05-13 15:48 ` Daniel Jacobowitz
2006-05-13 15:49 ` Bob Rossi
2006-05-13 17:11 ` Daniel Jacobowitz
2006-05-14 3:25 ` Bob Rossi
2006-05-14 4:17 ` Nick Roberts
2006-05-14 4:18 ` Eli Zaretskii
2006-05-14 5:01 ` Daniel Jacobowitz
2006-05-15 6:55 ` Nick Roberts
2006-05-15 13:35 ` Daniel Jacobowitz
2006-05-15 13:39 ` Bob Rossi
2006-05-15 15:04 ` Daniel Jacobowitz
2006-05-15 19:04 ` Jim Blandy
2006-05-15 13:37 ` Jim Blandy
2006-05-15 14:58 ` Bob Rossi
2006-05-15 18:50 ` Jim Blandy
2006-05-15 20:09 ` Bob Rossi
2006-05-15 18:42 ` PAUL GILLIAM
2006-05-15 19:18 ` Bob Rossi
2006-05-15 19:43 ` Daniel Jacobowitz
2006-05-15 20:05 ` Bob Rossi
2006-05-15 20:09 ` Daniel Jacobowitz
2006-05-15 20:20 ` Bob Rossi
2006-05-15 21:02 ` Daniel Jacobowitz [this message]
2006-05-15 21:08 ` Bob Rossi
2006-05-15 21:31 ` Daniel Jacobowitz
2006-05-15 21:33 ` Bob Rossi
2006-05-15 20:11 ` PAUL GILLIAM
2006-05-15 20:33 ` Bob Rossi
2006-05-15 21:52 ` Joel Brobecker
2006-05-15 22:40 ` Bob Rossi
2006-05-16 3:32 ` Nick Roberts
2006-05-18 1:40 ` Bob Rossi
2006-05-18 12:32 ` Jim Blandy
2006-05-18 7:28 ` Bob Rossi
2006-05-18 16:27 Alain Magloire
2006-05-18 16:55 ` Bob Rossi
2006-05-18 16:59 ` Andreas Schwab
[not found] ` <vt2bqtvl157.fsf@theseus.home.>
2006-05-18 17:44 ` Bob Rossi
2006-05-18 21:56 ` Jim Blandy
2006-05-19 1:19 ` Bob Rossi
2006-05-19 3:00 ` Daniel Jacobowitz
2006-05-19 12:49 ` Bob Rossi
2006-05-19 15:37 ` Daniel Jacobowitz
2006-05-19 15:56 ` Bob Rossi
2006-05-19 17:55 ` Jim Blandy
2006-05-19 19:22 ` Bob Rossi
2006-05-23 3:46 ` Jim Blandy
2006-05-18 22:51 ` Andreas Schwab
2006-05-18 23:25 ` Bob Rossi
2006-05-19 1:17 ` Andreas Schwab
2006-05-18 23:28 ` Jim Blandy
2006-05-19 0:59 ` Andreas Schwab
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=20060515202042.GA8673@nevyn.them.org \
--to=drow@false.org \
--cc=bob_rossi@cox.net \
--cc=gdb@sourceware.org \
--cc=pgilliam@us.ibm.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