This is the mail archive of the
mailing list for the Cygwin project.
Re: nm for .exe extensions?
- From: Bill Smith <bsmith at progress dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 7 Jun 2016 08:43:15 -0700 (MST)
- Subject: Re: nm for .exe extensions?
- Authentication-results: sourceware.org; auth=none
- References: <a66eaf9339774b6a8fbc1ab4b99f428d at ntmaexbe04 dot bedford dot progress dot com> <76282617-B02E-4782-B4A0-AEB3756DE152 at etr-usa dot com>
Warren Young-2 wrote
> On May 24, 2016, at 6:43 AM, Benjamin Cao <
> > 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!â
> $ make hello
> cc hello.c -o hello
> $ nm hello.exe | wc -l
> 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
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 ?
View this message in context: http://cygwin.1069669.n5.nabble.com/nm-for-exe-extensions-tp127152p127453.html
Sent from the Cygwin list mailing list archive at Nabble.com.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple