This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Stack traces and sections in PE/COFF

From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
To: binutils at sourceware dot org
Cc: Piotr Wyderski <piotr dot wyderski at gmail dot com>, Joe Abbey <joe dot abbey at gmail dot com>
Date: Tue, 3 Feb 2009 05:52:30 +0000
Subject: Re: Stack traces and sections in PE/COFF
References: <9f8a01cd0902020814k25d770e4kafa9f857049fe8b6@mail.gmail.com> <2ca21dcc0902021003w14db75f8h9b318e82c2019eb8@mail.gmail.com> <b2a052580902021012g6a2959f7p11023ea6efea52d9@mail.gmail.com>

Joe Abbey wrote:
> For documentation on the PE/COFF specification please see:

  Thanks, I do keep a copy or two lying around :)

> In Section 4.0

  As you say, it's unambiguously not permitted in executable images.  It all
works fine for .o files, but shouldn't be done at final link time.

  The bug is in coff_write_object_contents in bfd/coffcode.h, under control
of #ifdef COFF_LONG_SECTION_NAMES.  It blindly adds a long name to the string
table even if there isn't going to be one in the final image.

  Piotr, thanks for drawing this to our attention.  I'll prepare and test a
fix.  You could file a bug report in the sourceware.org bugzilla if you like
and add my email to the Cc list.

    cheers,
      DaveK

References:
- Re: Stack traces and sections in PE/COFF
  - From: Dave Korn
- Re: Stack traces and sections in PE/COFF
  - From: Joe Abbey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]