From: Bob Rossi <bob@brasko.net>
To: gdb@sources.redhat.com
Subject: Re: Driving gdb from a front end: how to send ctrl-c?
Date: Thu, 18 Mar 2004 04:13:00 -0000 [thread overview]
Message-ID: <20040318041317.GA10764@white> (raw)
In-Reply-To: <20040318040247.91931.qmail@web14104.mail.yahoo.com>
On Wed, Mar 17, 2004 at 08:02:47PM -0800, Marco Zandonadi wrote:
> Hello,
> I'm writing a front end for gdb that needs to work on
> Cygwin and Linux. I'm trying out Cygwin first. After
> reading several posts in the archives of this ML I
> came up with a small proof-of-concept program that:
> - sets up master and slave PTY
> - forks a process and executes gdb in it
> - sends a few commands to gdb
>
> Everything works ok except ctrl-c. Here is the
> sequence of commands my program is sending gdb:
> - b main
> - r
> - c
> - ctrl-c (ASCII char 3)
>
> I can see the proper output for all commands except
> ctrl-c. I guess this is because I missed some terminal
> settings.
>
> The other problem is that I get about 10 msgs like
> this:
> [tcsetpgrp failed in terminal_inferior: Operation not
> permitted]
>
> I attached the small cygwin program I talked about.
> Any help will be very much appreciated.
Are you sure you want a pseudo terminal between you and GDB?
If you do that, readline will be active. If you just use a normal pipe,
readline will not be active. Also, you can not send a signal to GDB when
readline is active, since it interprets the signals.
BTW, you should really check out how CGDB/TGDB works. It does exactly
what you want. Basically, you could take TGDB and modify it to do what
you want. Obviously TGDB is not supported by the GDB people :)
Bob Rossi
prev parent reply other threads:[~2004-03-18 4:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 4:02 Marco Zandonadi
2004-03-18 4:13 ` Bob Rossi [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=20040318041317.GA10764@white \
--to=bob@brasko.net \
--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