From: Bob Rossi <bob_rossi@cox.net>
To: PAUL GILLIAM <pgilliam@us.ibm.com>, gdb@sourceware.org
Subject: Re: invoking GDB from FE and signals
Date: Mon, 15 May 2006 21:33:00 -0000 [thread overview]
Message-ID: <20060515210902.GE21608@brasko.net> (raw)
In-Reply-To: <20060515210246.GA9737@nevyn.them.org>
On Mon, May 15, 2006 at 05:02:46PM -0400, Daniel Jacobowitz wrote:
> On Mon, May 15, 2006 at 04:34:26PM -0400, Bob Rossi wrote:
> > > > 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.
> >
> > I desire that CGDB works exactly the same as if the user was at the
> > terminal with GDB. So, ^c probably is what I want, since it's what
> > the user would have to do anyways. Does this sound correct to you?
>
> The interrupt character is actually configurable; C-c might not
> generate an interrupt, et cetera. All this stuff is very complex :-)
>
> (man stty, search for intr)
Thanks, I've spent a lot of time dealing with this in the past. A good
primer for me was Advanced Programming in the UNIX Environment, written
by W Richard Stevens.
Unless an example can be given otherwise, I think writing the char to
the PTY is the best solution. This provides hopefully the exact same
response the user would get while sitting in front of the PTY. However,
you recomendation alerts me that I will need to make sure that the
created PTY has the same values set as the PTY on CGDB's STDIN.
Hopefully, I'll have some solution soon. I think this is a wealth of
information, would all of these details be welcome in the MI manual,
under "Starting and controlling GDB"?
Thanks a lot,
Bob Rossi
next prev parent reply other threads:[~2006-05-15 21:08 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
2006-05-15 21:08 ` Bob Rossi
2006-05-15 21:31 ` Daniel Jacobowitz
2006-05-15 21:33 ` Bob Rossi [this message]
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=20060515210902.GE21608@brasko.net \
--to=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