From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Doug Evans <dje@google.com>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA] Fix too many "no debugging symbols found" warnings.
Date: Fri, 05 Jun 2009 22:18:00 -0000 [thread overview]
Message-ID: <m3hbyus4x1.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200906051949.45647.pedro@codesourcery.com> (Pedro Alves's message of "Fri\, 5 Jun 2009 19\:49\:44 +0100")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
Tom> IMO, the ideal would be to share objfiles across inferiors (perhaps a
Tom> big task in itself) and then issue this warning at most once per
Tom> objfile. That way the user won't see 1000 warnings for /lib/libc.so.
Pedro> For true/always/full sharing, I'm thinking that we'd have to
Pedro> rework how gdb addresses symbol values (we relocate everything
Pedro> early; we'd have to apply relocation offsets on demand), and,
Pedro> we do some sorting of symbols, since sections may end up loaded
Pedro> at different relative offsets within the same objfile for
Pedro> different inferiors, in some targets.
Yeah. I was thinking of perhaps splitting objfile in two, and moving
the relocated bits into a per-inferior handle, which points to the
abstract objfile.
But, this is just a vague thought. And, we've been talking a bit in
Archer-land about some more drastic changes to the symbol tables
(e.g., getting rid of psymtabs for dwarf), and this would probably
interact with that as well.
Tom
next prev parent reply other threads:[~2009-06-05 22:18 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 [this message]
2009-06-19 0:48 ` Doug Evans
2009-06-22 17:54 ` Tom Tromey
2009-06-22 19:35 ` Pedro Alves
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=m3hbyus4x1.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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