Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: $_ and info breakpoint [PATCH]
Date: Wed, 11 Jul 2007 00:35:00 -0000	[thread overview]
Message-ID: <18068.9698.320580.484432@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20070710235142.GA6510@caradoc.them.org>

 > They don't have a very nice console, but it's there.  If you click on
 > the tab that your program I/O isn't on, you can type commands at GDB
 > and it will get them (it's in the Consoles pane, but a separate
 > sub-pane or view or whatever the heck they call it).

OK, I've found it now - there's no (gdb) prompt.  I thought perhaps there
would be the same problem with $_, but that doeasn't appear to be the case.

I don't really understand how they control the separate terminal for program
I/O as the program is a child of GDB, and not Eclipse, so presumably Eclipse
can't create a terminal for it.  In my migratory mode I use sleep to create a
terminal and send program I/O to that, but this seems a bit of a hack.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2007-07-11  0:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18064.7905.924535.720690@kahikatea.snap.net.nz>
     [not found] ` <20070709115647.GC3095@caradoc.them.org>
2007-07-10  0:22   ` Nick Roberts
2007-07-10  1:43     ` Daniel Jacobowitz
2007-07-10  3:20       ` Eli Zaretskii
2007-07-10 11:20         ` Daniel Jacobowitz
2007-07-10 23:11           ` Nick Roberts
2007-07-10 23:51             ` Daniel Jacobowitz
2007-07-11  0:35               ` Nick Roberts [this message]
2007-07-11 11:32                 ` Daniel Jacobowitz
2007-07-11 18:15     ` Jim Blandy
2007-07-11 22:56       ` $_ and info breakpoint [PATCH: doco] Nick Roberts
2007-07-12  3:19         ` Eli Zaretskii

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=18068.9698.320580.484432@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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