Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: a2782@dis.ulpgc.es, gdb@sources.redhat.com
Subject: Re: Emacs and GDB
Date: Sat, 23 Nov 2002 15:52:00 -0000	[thread overview]
Message-ID: <vt2fztr272n.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <9743-Sat23Nov2002223357+0200-eliz@is.elta.co.il>

"Eli Zaretskii" <eliz@is.elta.co.il> writes:

> > Date: Sat, 23 Nov 2002 12:57:05 GMT
> > From: a2782@dis.ulpgc.es
> > 
> > Any idea about how can I do this emacs-style invocation in (Kylix) C++? 
> > I want to execute GDB and redirect its input to the output of my 
> > program in C++ (in order to send commands to GDB); and its output to 
> > the input of my C++ program (in order to parse the information which 
> > GDB returns).
> 
> Why not do what Emacs does: create a pipe for communications between
> GDB and your program, then fork/exec GDB and redirect its standard
> streams to the pipe using dup2/dup system calls?

Actually, Emacs creates a pseudo-tty, and runs GDB there.  That allows
Emacs to send a SIGINT when the user types 'C-c C-c', and things like
that.


  reply	other threads:[~2002-11-23 23:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-23  2:36 a2782
2002-11-23  3:36 ` Eli Zaretskii
2002-11-23  3:59   ` a2782
2002-11-23 12:34     ` Eli Zaretskii
2002-11-23 15:52       ` Jim Blandy [this message]
2002-11-23 21:55         ` Eli Zaretskii
2002-11-25  6:50     ` Kris Warkentin
2002-12-05 16:56     ` Fernando Nasser
2002-12-09  9:40       ` a2782
2002-12-09 10:12         ` Keith Seitz
2008-11-06  7:07 emacs and gdb Dave Milter
2008-11-06  9:16 ` Andreas Schwab
2008-11-06  9:40   ` Dave Milter
2008-11-06  9:44     ` Andreas Schwab
2008-11-06 10:31       ` Dave Milter
2009-01-25  1:17         ` Nick Roberts

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=vt2fztr272n.fsf@zenia.red-bean.com \
    --to=jimb@redhat.com \
    --cc=a2782@dis.ulpgc.es \
    --cc=eliz@is.elta.co.il \
    --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