From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: mec.gnu@mindspring.com, nathanw@wasabisystems.com,
gdb@sources.redhat.com
Subject: Re: "break main; run" test
Date: Sun, 11 Jan 2004 15:59:00 -0000 [thread overview]
Message-ID: <400172D7.6030403@gnu.org> (raw)
In-Reply-To: <6654-Sat10Jan2004135841+0200-eliz@elta.co.il>
>> Date: Fri, 09 Jan 2004 11:56:06 -0500
>> From: Andrew Cagney <cagney@gnu.org>
>>
>> Should note that I intend tweaking the doco so that "backtrace", instead
>> of "print args" is used. I suspect that "backtrace" is GDB's second
>> most popular user command
>
>
> How about doing both bt and p? I think they are both very central to
> any debugging, no matter what user polls (if we have them) say.
M'kay, and perhaps break in something other than main - a backtrace when
in main isn't very interesting :-)
Andrew
next prev parent reply other threads:[~2004-01-11 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 3:16 Michael Elizabeth Chastain
2004-01-09 8:52 ` Eli Zaretskii
2004-01-09 16:56 ` Andrew Cagney
2004-01-10 12:02 ` Eli Zaretskii
2004-01-11 15:59 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-09 23:27 Michael Elizabeth Chastain
2004-01-09 22:25 Michael Elizabeth Chastain
2004-01-09 22:55 ` Andrew Cagney
2004-01-09 3:04 Nathan J. Williams
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=400172D7.6030403@gnu.org \
--to=cagney@gnu.org \
--cc=eliz@elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.com \
--cc=nathanw@wasabisystems.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