From: Jim Blandy <jimb@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] add-symbol-file-from-memory command
Date: Thu, 08 Apr 2004 22:13:00 -0000 [thread overview]
Message-ID: <vt265ca86j2.fsf@zenia.home> (raw)
In-Reply-To: <200404082047.i38Klcqb010158@magilla.sf.frob.com>
Roland McGrath <roland@redhat.com> writes:
> I updated my tree and made a new diff for add-symbol-file-from-memory,
> though there were no conflicts to resolve so it's not materially different
> >From the last version of this patch I posted. It still works with today's
> gdb. Several people have looked at this code before. It just needs
> authoritative approval to go in. If anyone has any reservations, I haven't
> heard them articulated. As I've mentioned before, the new command itself
> is not the motivation for the new function. It's the final piece of
> necessary infrastructure for vsyscall DSO support for Linux targets.
> (After this, the only thing needed is the glue to check for AT_SYSINFO at
> the right time.)
This looks fine. Two suggestions:
- Would it work to completely replace
symbol_file_add_with_addrs_or_offsets's 'name' argument with the
abfd argument, and then just use bfd_get_filename? It looks to me
like the only affect would be that the tilde-expanded, path-searched
filename would appear in messages, which seems like a good thing.
- Since the command isn't something that ordinary users are really
going to want themselves, but is more for the benefit of GDB
developers, should be a 'maint' subcommand?
next prev parent reply other threads:[~2004-04-08 22:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 20:47 Roland McGrath
2004-04-08 22:13 ` Jim Blandy [this message]
2004-04-08 22:28 ` Roland McGrath
2004-04-08 22:32 ` Daniel Jacobowitz
2004-04-08 22:35 ` Andrew Cagney
2004-04-08 22:42 ` Roland McGrath
2004-04-15 18:52 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-04-08 22:38 Roland McGrath
2004-04-15 18:11 ` Jim Blandy
2004-04-15 18:49 ` Andrew Cagney
2004-04-15 21:42 ` Roland McGrath
2004-02-12 0:34 Roland McGrath
2004-02-13 15:54 ` Andrew Cagney
2004-02-13 19:13 ` Roland McGrath
2004-02-02 3:38 Roland McGrath
2004-02-02 4:06 ` Daniel Jacobowitz
2004-02-02 4:47 ` Roland McGrath
2004-02-02 15:02 ` Daniel Jacobowitz
2004-02-02 23:31 ` Roland McGrath
2004-02-02 23:34 ` Daniel Jacobowitz
2004-02-02 6:19 ` Eli Zaretskii
2004-02-02 7:35 ` Roland McGrath
2004-02-02 17:29 ` Eli Zaretskii
2003-10-03 4:27 Roland McGrath
2003-10-03 21:41 ` Jim Blandy
2003-10-03 21:45 ` Daniel Jacobowitz
2003-10-03 22:08 ` Roland McGrath
2003-10-03 22:19 ` Elena Zannoni
2003-10-03 23:00 ` Roland McGrath
2003-10-04 12:57 ` Elena Zannoni
2003-10-04 20:14 ` Roland McGrath
2003-10-07 1:42 ` Andrew Cagney
2003-10-03 22:34 ` Andrew Cagney
2003-10-03 23:02 ` Roland McGrath
2003-10-04 14:39 ` Andrew Cagney
2003-10-06 15:30 ` Jim Blandy
2003-10-06 15:43 ` Daniel Jacobowitz
2003-10-06 19:57 ` Roland McGrath
2003-10-07 23:32 ` Michael Snyder
2003-05-20 7:01 Roland McGrath
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=vt265ca86j2.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=roland@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