This is the mail archive of the
mailing list for the GDB project.
Re: DWARF 2 sections and padding ?
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Brian Ford <ford at vss dot fsi dot com>
- Cc: gdb at sources dot redhat dot com, binutils at sources dot redhat dot com
- Date: Fri, 21 Feb 2003 12:16:27 -0500
- Subject: Re: DWARF 2 sections and padding ?
- References: <Pine.GSO.4.44.0302210931590.19283-100000@eos>
- Reply-to: binutils at sources dot redhat dot com
On Fri, Feb 21, 2003 at 10:16:49AM -0600, Brian Ford wrote:
> I am trying to add DWARF 2 support for PE/COFF on Cygwin. PE/COFF
> sections must be aligned to 512 byte boundaries. This extra padding
> confuses the DWARF 2 parsing routines because they use the sections
> raw_size, thus parsing an invalid compilation unit header (all
> The actual, smaller size is available in the section header. I am
> confused about what the cooked_size is supposed to mean. It is currently
> zero, but I think it could contain the smaller virtual size.
> I have read the DWARF spec several times, and although it discusses this
> issue briefly for some debugging sections, it is unclear to me how this
> should really work. Unless I try to arrange for the producer (gcc) to
> pad the compilation units with zeros instead of having bfd pad the end of
> the sections, I don't know how to proceed.
> I would like to just use an alternate size instead of the raw size (cooked
> maybe?) but I don't know how this would affect other targets and I don't
> want a PE specific hack in DWARF parsing code.
> Any ideas? Thanks.
I don't see why the raw size should include the padding; that should
just be used when _placing_ sections. But this is a binutils/bfd
issue; redirected to that list.
MontaVista Software Debian GNU/Linux Developer