Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Philippe Elie <phil.el@wanadoo.fr>
Cc: graydon@redhat.com, oprofile-list@sourceforge.net,
	binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: separated debuginfo patch
Date: Fri, 11 Jul 2003 16:01:00 -0000	[thread overview]
Message-ID: <m3brw1vzby.fsf@redhat.com> (raw)
In-Reply-To: <3F062F6C.7050106@wanadoo.fr> (Philippe Elie's message of "Sat, 05 Jul 2003 01:52:44 +0000")

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.


> > We just need to agree on the format and name of the timestamp
> > section in the debuginfo file, and how to distinguish old
> > .gnu-debuglink sections (only containing a crc) from new ones
> > (containing a crc and a timestamp).
> 
> I disambiguate the two case by looking the section size. See
> bfd.diff, it's a bit ugly but I don't see how I can deal cleanly
> with this problem.

Actually I rather like this solution.  Adding the timestamp as an
extra field at the end of the .gnu-debuglink section seems rather
elegant and it eliminates the need for a new section.

Some comments on the patch:
      
> + #define GNU_DEBUGLINK_TIMESTAMP ".gnu_debuglink_timestamp"

This is not needed, since the timestamp is going to be held in the
.gnu-debuglink section.


>   INTERNAL_FUNCTION
> + 	bfd_get_debug_timestamp_info
> + 
> + SYNOPSIS
> + 	bfd_boolean bfd_get_debug_timestamp_info
> + 	  (bfd *abfd, unsigned long *timestamp);
> + 
> + DESCRIPTION
> + 	fetch the timestamp for any separate debuginfo associated with
> + 	@var{abfd}.

Similarly this function should extract the timestamp from the
.gnu-debuglink section.


> +   printf("try %s %ld\n", name, timestamp);

I assume that this is left over debugging ?

> !   debuglink_size += 8;

We ought to add a comment explaining why the value 8 is used here.


Overall though I like the patch and the solution.  If we can get the
GDB maintainers to agree (or at least not object to) adding the extra
field at the end of the .gnu-debuglink section then I would be happy
to review a final version of the patch.  (Note - you will need a FSF
copyright assignment as well...)

Cheers
        Nick


  reply	other threads:[~2003-07-11 16:01 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 [this message]
2003-07-18  6:42               ` Jim Blandy
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=m3brw1vzby.fsf@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=graydon@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