From: Pedro Alves <pedro@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Doug Evans <dje@google.com>, Eli Zaretskii <eliz@gnu.org>,
"gdb-patches" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Fix too many "no debugging symbols found" warnings.
Date: Mon, 22 Jun 2009 19:35:00 -0000 [thread overview]
Message-ID: <200906222035.48910.pedro@codesourcery.com> (raw)
In-Reply-To: <m31vpcp34n.fsf@fleche.redhat.com>
On Monday 22 June 2009 18:52:40, Tom Tromey wrote:
> >>>>> "Doug" == Doug Evans <dje@google.com> writes:
>
> Doug> What's the reason for passing from_tty=0 to symbol_file_add_main from
> Doug> captured_main?
>
> For questions like this I think the only thing to do is some
> archaeology. I looked, though, and this seems to have been 0 all the
> way back to 1.1 in the src repository. (I don't think I have ready
> access to the older Cygnus repository any more.)
You can go further back by looking at the old-releases, found through:
http://sourceware.org/gdb/download/
On gdb-2.51, I see this:
if (!strcmp (arg, "-se"))
{
exec_file_command (argv[i], !batch);
symbol_file_command (argv[i], !batch);
}
At revision 1.1 in CVS we have:
exec_file_command (execarg, !batch);
symbol_file_command (symarg, 0);
So at some point in time, the from_tty argument was changed to
a hardcoded 0.
Why that was so, I don't know. I like gdb's output with
Doug's suggestion.
(BTW, looking through such old gdb's sources can be
quite informative sometimes, it's like looking at a
smaller prototype sketch of current gdb. I keep copies
of those sources around myself, and sometimes peek them.)
--
Pedro Alves
next prev parent reply other threads:[~2009-06-22 19:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 23:24 Doug Evans
2009-05-25 3:20 ` Eli Zaretskii
2009-05-25 16:07 ` Doug Evans
2009-06-04 20:34 ` Tom Tromey
2009-06-04 21:20 ` Pedro Alves
2009-06-05 18:19 ` Tom Tromey
2009-06-05 18:49 ` Pedro Alves
2009-06-05 22:18 ` Tom Tromey
2009-06-19 0:48 ` Doug Evans
2009-06-22 17:54 ` Tom Tromey
2009-06-22 19:35 ` Pedro Alves [this message]
2009-06-30 21:49 ` Doug Evans
2009-06-30 21:55 ` Pedro Alves
2009-06-30 22:20 ` Doug Evans
2009-07-01 2:29 ` Tom Tromey
2009-07-01 3:13 ` Eli Zaretskii
2009-07-01 3:47 ` Doug Evans
2009-07-01 17:48 ` Eli Zaretskii
2009-07-01 17:53 ` Doug Evans
2009-07-01 18:01 ` Pedro Alves
2009-07-01 19:55 ` Doug Evans
2009-07-02 13:26 ` Pedro Alves
2009-07-02 20:08 ` Doug Evans
2009-07-02 22:43 ` Pedro Alves
2009-07-11 4:22 ` Doug Evans
2009-07-20 13:21 ` Pedro Alves
2009-07-23 18:57 ` Doug Evans
2009-07-27 17:15 ` Tom Tromey
2009-08-24 22:02 ` Doug Evans
2009-08-25 3:47 ` Eli Zaretskii
2009-08-27 19:11 ` Tom Tromey
2009-08-27 23:39 ` Doug Evans
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=200906222035.48910.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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