From: Jim Blandy <jimb@redhat.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Philippe Elie <phil.el@wanadoo.fr>,
graydon@redhat.com, oprofile-list@sourceforge.net,
binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: separated debuginfo patch
Date: Fri, 18 Jul 2003 06:42:00 -0000 [thread overview]
Message-ID: <vt265m0ibas.fsf@zenia.home> (raw)
In-Reply-To: <m3brw1vzby.fsf@redhat.com>
Nick Clifton <nickc@redhat.com> writes:
> Hi Philippe,
>
> Sorry for the long delay in replying - I have been very busy over
> the last few weeks.
>
>
> > I need to know how GDB guys want I deal with the gdb part, for now
> > gdb.diff just remove (#if 0) all duplicated code from bfd and use
> > bfd_follow_gnu_debuglink() to retrieve the debug info file. Is it
> > ok to remove this code or must I update the duplicated code according
> > to the change in bfd ?
>
> Well this is up to the gdb maintainers to decide, but it certainly
> seems like a good idea to avoid the code duplication.
Sure, the plan has long been for GDB to just use the function in BFD.
The code was added to GDB before BFD; that's the only reason it's
there at all.
Just to be sure --- under this arrangement, the old-style debug links
will continue to work, right?
One could use something like '(date; ps auxww; vmstat) | md5sum | cut
-b 1-33' to generate nice unique ID strings.
next prev parent reply other threads:[~2003-07-18 6:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wuf3s4q3.fsf@dub.venge.net>
[not found] ` <3F02B1A5.5000102@wanadoo.fr>
[not found] ` <87adbwpkhj.fsf@dub.venge.net>
[not found] ` <3F03EB19.4090801@wanadoo.fr>
2003-07-04 10:04 ` Nick Clifton
2003-07-04 23:38 ` Philippe Elie
2003-07-04 23:40 ` Philippe Elie
2003-07-11 16:01 ` Nick Clifton
2003-07-18 6:42 ` Jim Blandy [this message]
2003-07-18 8:06 ` Nick Clifton
2003-07-18 13:42 ` Andrew Cagney
2003-07-18 14:03 ` Daniel Jacobowitz
2003-07-18 14:41 ` graydon hoare
2003-07-18 7:32 Michael Elizabeth Chastain
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=vt265m0ibas.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=graydon@redhat.com \
--cc=nickc@redhat.com \
--cc=oprofile-list@sourceforge.net \
--cc=phil.el@wanadoo.fr \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).