public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Cc: Kai Tietz <ktietz70@googlemail.com>
Subject: Re: Problem with nm in binutils-2.25-2 on x86
Date: Fri, 09 Oct 2015 10:30:00 -0000	[thread overview]
Message-ID: <5617974E.10705@gmail.com> (raw)
In-Reply-To: <561684E7.5010608@cornell.edu>

[-- Attachment #1: Type: text/plain, Size: 666 bytes --]


> $ nm -l a.exe
> 00406000 b .bssBFD: Dwarf Error: Could not find abbrev number 120.
> 00406018 b .bssBFD: Dwarf Error: Could not find abbrev number 120.
> [...]
> 00406040 b _u.25303BFD: Dwarf Error: Could not find abbrev number 120.
> 00401000 T _WinMainCRTStartup
> /usr/src/debug/cygwin-2.2.1-1/winsup/cygwin/crt0.c:23
> 004070b8 i fthunkBFD: Dwarf Error: Could not find abbrev number 120.
> 00407074 i hnameBFD: Dwarf Error: Could not find abbrev number 120.
> 
> Ken

Kai is of the opinion that rebuilding the gcc, CRT, Cygwin and
everything in between be rebuilt with the new binutils to solve the issue.

Might be a huge undertaking.




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2015-10-09 10:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 13:12 Ken Brown
2015-10-07  9:57 ` JonY
2015-10-08  9:35   ` JonY
2015-10-08 14:59     ` Ken Brown
2015-10-09 10:30       ` JonY [this message]
2015-10-09 15:38         ` Ken Brown
2015-10-09 23:55           ` JonY
2015-10-10 15:04             ` JonY
2015-10-11  4:25               ` JonY
2015-10-11 13:52                 ` Ken Brown
2015-11-20 10:53                   ` Marco Atzeri
2015-11-20 13:55                     ` JonY
2015-11-24 18:24                       ` Marco Atzeri
2015-11-25  2:29                         ` JonY

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=5617974E.10705@gmail.com \
    --to=10walls@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=ktietz70@googlemail.com \
    /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).