From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: nm for .exe extensions?
Date: Tue, 24 May 2016 13:50:00 -0000 [thread overview]
Message-ID: <76282617-B02E-4782-B4A0-AEB3756DE152@etr-usa.com> (raw)
In-Reply-To: <a66eaf9339774b6a8fbc1ab4b99f428d@ntmaexbe04.bedford.progress.com>
On May 24, 2016, at 6:43 AM, Benjamin Cao <becao@progress.com> 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.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
WARNING: multiple messages have this Message-ID
From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: nm for .exe extensions?
Date: Tue, 24 May 2016 14:34:00 -0000 [thread overview]
Message-ID: <76282617-B02E-4782-B4A0-AEB3756DE152@etr-usa.com> (raw)
Message-ID: <20160524143400.0J6YHi6cgzn4DeIK_0IciyaUuEPGnZA3_0Bjm1XKN2c@z> (raw)
In-Reply-To: <a66eaf9339774b6a8fbc1ab4b99f428d@ntmaexbe04.bedford.progress.com>
On May 24, 2016, at 6:43 AM, Benjamin Cao <becao@progress.com> 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.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
WARNING: multiple messages have this Message-ID
From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: nm for .exe extensions?
Date: Tue, 24 May 2016 16:56:00 -0000 [thread overview]
Message-ID: <76282617-B02E-4782-B4A0-AEB3756DE152@etr-usa.com> (raw)
Message-ID: <20160524165600.cUkMGqbFXIjpnvysV1i1p53TZ5xzX45frzTKevOJHxo@z> (raw)
In-Reply-To: <a66eaf9339774b6a8fbc1ab4b99f428d@ntmaexbe04.bedford.progress.com>
On May 24, 2016, at 6:43 AM, Benjamin Cao <becao@progress.com> 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.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-05-24 13:29 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 [this message]
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
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=76282617-B02E-4782-B4A0-AEB3756DE152@etr-usa.com \
--to=wyml@etr-usa.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).