This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: "break main; run" test

From: Andrew Cagney <cagney at gnu dot org>
To: Eli Zaretskii <eliz at elta dot co dot il>
Cc: mec dot gnu at mindspring dot com, nathanw at wasabisystems dot com,gdb at sources dot redhat dot com
Date: Sun, 11 Jan 2004 10:59:19 -0500
Subject: Re: "break main; run" test
References: <20040109031621.412084B35A@berman.michael-chastain.com> <2914-Fri09Jan2004104913+0200-eliz@elta.co.il> <3FFEDD26.3080304@gnu.org> <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

References:
- Re: "break main; run" test
  - From: Michael Elizabeth Chastain
- Re: "break main; run" test
  - From: Eli Zaretskii
- Re: "break main; run" test
  - From: Andrew Cagney
- Re: "break main; run" test
  - From: Eli Zaretskii

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]