This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [objcopy]: zero to three bytes of padding in .gnu_debuglink section
- From: T Majchrowski <bugtracker at majchrowski dot co dot uk>
- To: Majcher <bugtracker at majchrowski dot co dot uk>, binutils at sourceware dot org
- Cc: Alan Modra <amodra at gmail dot com>
- Date: Wed, 6 Apr 2011 17:54:59 +0200
- Subject: Re: [objcopy]: zero to three bytes of padding in .gnu_debuglink section
- References: <31316785.post@talk.nabble.com> <20110406074802.GQ19002@bubble.grove.modra.org>
2011/4/6 Alan Modra <amodra@gmail.com>
>
> On Mon, Apr 04, 2011 at 10:31:41AM -0700, Majcher wrote:
> > I found that .gnu_debuglink. section contains zero to three bytes of padding
> > just after filename. I recognized that this padding may be different
> > depending on which host is used to add gnu_debuglink via objcopy
> > --add-gnu-debuglink. Is there any way to provide always a fixed value of
> > that padding?
>
> No.
>
I checked sources, it seems so that it would quite easy to achieve
just by changing
FROM: contents = malloc (debuglink_size );
TO: contents = calloc (debuglink_size,sizeof(char) );
in bfd/opncls.c
regards, Majcher.