From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: nm for .exe extensions?
Date: Tue, 07 Jun 2016 20:32:00 -0000 [thread overview]
Message-ID: <20160607203153.GE3023@calimero.vinschen.de> (raw)
In-Reply-To: <CAFo71_6UOvDv2eNRWVix96iJDXw3+bXg1CxoMe-WRxFy8+aXyQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1836 bytes --]
On Jun 7 19:23, Ismail Donmez wrote:
> Hi,
>
> On Tue, Jun 7, 2016 at 7:12 PM, Corinna Vinschen
> <corinna-cygwin@cygwin.com> wrote:
> > On Jun 7 08:43, Bill Smith wrote:
> >> Warren Young-2 wrote
> >> > On May 24, 2016, at 6:43 AM, Benjamin Cao <
> >>
> >> > becao@
> >>
> >> > > wrote:
> >> >>
> >> >> The executable, when run with nm in Cygwin, results in a "no symbols"
> >> >> result, whereas it generates a symbol table in unix.
> >> >
> >> > That’s not what I see here. Given hello.c containing a “Hello, world!”
> >> > program:
> >> >
> >> > $ make hello
> >> > cc hello.c -o hello
> >> > $ nm hello.exe | wc -l
> >> > 389
> >> >
> >> > If I strip the exe, I get “No symbols,” as expected. There’s no reason a
> >> > finished executable should have much in the way of exported symbols
> >> > without debug info, since it is self-contained. You would only expect to
> >> > get useful output from nm on a stripped binary if it’s an object file or a
> >> > DLL.
> >>
> >> Hi, I'm picking this issue up from my colleague, Ben Cao. We're using
> >> Visual Studio C++ to compile the executables/objects. Is the issue that
> >> Visual Studio places the information in the .pdb file? That's why nm
> >> doesn't display any info on an *.exe ?
> >
> > PDB is an undocumented and potentially patent-encumbered format, that's
> > why the binutils tools can't read or write it.
>
> This will hopefully be no longer true in the future:
> https://github.com/Microsoft/microsoft-pdb
Interesting. Now somebody just have to pick this up and port it to
binutils... (the good old SHTDI meme ;))
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-07 20:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 12:46 Benjamin Cao
2016-05-24 13:16 ` Marco Atzeri
2016-05-24 13:29 ` Marco Atzeri
2016-05-24 13:57 ` Marco Atzeri
2016-05-24 16:44 ` Marco Atzeri
2016-05-24 13:50 ` Warren Young
2016-05-24 14:34 ` Warren Young
2016-05-24 16:56 ` Warren Young
2016-06-07 15:43 ` Bill Smith
2016-06-07 16:12 ` Corinna Vinschen
2016-06-07 16:24 ` Ismail Donmez
2016-06-07 20:32 ` Corinna Vinschen [this message]
2016-05-24 14:36 ` Ken Brown
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=20160607203153.GE3023@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.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).