From: Marco Molteni <molter@tin.it>
To: Russell Shaw <rjshaw@netspace.net.au>
Cc: gdb@sources.redhat.com
Subject: Re: Learning gdb
Date: Mon, 27 Dec 2004 18:10:00 -0000 [thread overview]
Message-ID: <20041227190834.169ac92d.molter@tin.it> (raw)
In-Reply-To: <41CD4BE3.6040802@netspace.net.au>
On Sat, 25 Dec 2004 22:15:47 +1100
Russell Shaw <rjshaw@netspace.net.au> wrote:
[..]
> What's a good way of printing messages from my own printfs in the
> source without getting the output mixed up with the console output
> of gdb? (in an x-windows environment)
man gdb:
-tty=device
Run using device for your program's standard input and output.
so in the xterm you want to use for your printfs, you issue the "tty"
command and use the value you get for gdb:
molter@gattaccio[~]$ tty
/dev/ttyp1
on another xterm:
gdb -tty=/dev/ttyp1
marco
--
Very graphic, classical but efficient.
prev parent reply other threads:[~2004-12-27 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-25 11:12 Russell Shaw
2004-12-27 18:10 ` Marco Molteni [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=20041227190834.169ac92d.molter@tin.it \
--to=molter@tin.it \
--cc=gdb@sources.redhat.com \
--cc=rjshaw@netspace.net.au \
/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