From: Russell Shaw <rjshaw@netspace.net.au>
To: gdb@sources.redhat.com
Subject: Learning gdb
Date: Sat, 25 Dec 2004 11:12:00 -0000 [thread overview]
Message-ID: <41CD4BE3.6040802@netspace.net.au> (raw)
Hi,
I'm stepping thru gdb (gdb-6.3 on debian) using ddd/gdb. I got to
tui_command_loop() in tui-interp.c, but stepping thru gets a bit
tedious then.
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)
next reply other threads:[~2004-12-25 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-25 11:12 Russell Shaw [this message]
2004-12-27 18:10 ` Marco Molteni
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=41CD4BE3.6040802@netspace.net.au \
--to=rjshaw@netspace.net.au \
--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