From: "Eli Zaretskii" <eliz@elta.co.il>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: gdb@sources.redhat.com, nathanw@wasabisystems.com
Subject: Re: "break main; run" test
Date: Fri, 09 Jan 2004 08:52:00 -0000 [thread overview]
Message-ID: <2914-Fri09Jan2004104913+0200-eliz@elta.co.il> (raw)
In-Reply-To: <20040109031621.412084B35A@berman.michael-chastain.com> (mec.gnu@mindspring.com)
> Date: Thu, 8 Jan 2004 22:16:21 -0500 (EST)
> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
>
> > When people refer to the test of starting gdb on a program, setting a
> > breakpoint on "main", and running to that point, is there a particular
> > standard test program in mind? "Hello world"? The GDB binary itself?
>
> You are right; it is ambiguous.
Seconded. Perhaps we should replace that language with something less
ambiguous.
> To me, it usually means "the gdb binary itself", since the gdb binary is
> a large program and it's guaranteed to exist. Sometimes it means
> "hello world", and sometimes it means "any random program".
It should IMHO preferably be some non-trivially large program, as some
subtle problems don't get expiosed unless GDB needs to deal with
complex debug info structures. It certainly cannot be a program with
no debug info, since then it's not guaranteed that GDB will know where
to find the symbol `main'.
next prev parent reply other threads:[~2004-01-09 8:52 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 [this message]
2004-01-09 16:56 ` Andrew Cagney
2004-01-10 12:02 ` Eli Zaretskii
2004-01-11 15:59 ` Andrew Cagney
-- 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=2914-Fri09Jan2004104913+0200-eliz@elta.co.il \
--to=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