From: Jim Blandy <jimb@codesourcery.com>
To: Bob Rossi <bob_rossi@cox.net>
Cc: Nick Roberts <nickrob@snap.net.nz>, gdb@sourceware.org
Subject: Re: invoking GDB from FE and signals
Date: Mon, 15 May 2006 19:04:00 -0000 [thread overview]
Message-ID: <vt2y7x36sg3.fsf@theseus.home.> (raw)
In-Reply-To: <20060515133536.GF13445@brasko.net> (Bob Rossi's message of "Mon, 15 May 2006 09:35:36 -0400")
Bob Rossi <bob_rossi@cox.net> writes:
> On Sun, May 14, 2006 at 12:16:53AM -0400, Daniel Jacobowitz wrote:
>> On Sun, May 14, 2006 at 09:57:00AM +1200, Nick Roberts wrote:
>> > does it do when SIGINT is read" (which is sent by ~c^c). Well it just works
>> > like it does in a terminal but then I was surprised when Daniel said:
>> >
>> > When the inferior is running and you press Control-C, the signal goes to
>> > the inferior, not to GDB.
>> >
>> > because I had thought it was the other way round and GDB could decide whether
>> > to pass the signal on to the inferior or not according to the output of
>> > "info signal".
>>
>> Job control signals are funny. The C-c sends a signal to the process
>> group in control of the current terminal, and when the inferior is
>> running, GDB makes sure that it "owns" the terminal (so that it won't
>> e.g. be automatically stopped with SIGTTIN if it tries to read()).
>>
>> This all predates 'set tty' of course.
>
> O, right. The tty command. I definatly use that for the inferior which I
> believe emacs does not. Nick, do you know if emacs uses the 'set tty'
> command?
When you use GDB in the normal way, 'M-x gdb', it doesn't.
next prev parent reply other threads:[~2006-05-15 18:42 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 [this message]
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
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=vt2y7x36sg3.fsf@theseus.home. \
--to=jimb@codesourcery.com \
--cc=bob_rossi@cox.net \
--cc=gdb@sourceware.org \
--cc=nickrob@snap.net.nz \
/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