X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:message-id:in-reply-to:references
	:subject:mime-version:content-type:content-transfer-encoding; q=
	dns; s=default; b=p6REzOwe/23sEU38Pf+fHoVggSyoda0D7BkCIDib5DEm89
	y/6pjTGsA1y3MpBwM5McgwyK44QfiMhItgRxJ0qISBkzlse6K0/pfTJ9OBvu4CCY
	pvCHvNV+gk3KmMwVbfvSPLc4lkmTctc3CSk3A/nKxE3h18m13F3ix+PoGDWL4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:message-id:in-reply-to:references
	:subject:mime-version:content-type:content-transfer-encoding; s=
	default; bh=Ab9YHbKqm3kNHWIW0JCujGCSODM=; b=n1rJx3goT5eN4kcfiUOx
	q6IYfzoqCvyU54xfZFAPaL1MVLqY2mAP0Oc/3ppFANaBS8AcQmd/qRtfgEtl3QCm
	nT+8Gz3ZhjIXaN5CeFJbI5BHKRwbeR5BO+fcfaiPTnaYVjv6bXqvUREvzKvIfRPc
	/SBOVlUa/fG+0mtCGB3QudE=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=2.6 required=5.0 tests=BAYES_50,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL,URI_HEX autolearn=no version=3.3.2 spammy=cao, benjamin, Benjamin, UD:nabble.com
X-HELO: mbob.nabble.com
Date: Tue, 7 Jun 2016 08:43:15 -0700 (MST)
From: Bill Smith <bsmith AT progress DOT com>
To: cygwin AT cygwin DOT com
Message-ID: <1465314195730-127453.post@n5.nabble.com>
In-Reply-To: <76282617-B02E-4782-B4A0-AEB3756DE152@etr-usa.com>
References: <a66eaf9339774b6a8fbc1ab4b99f428d AT ntmaexbe04 DOT bedford DOT progress DOT com> <76282617-B02E-4782-B4A0-AEB3756DE152 AT etr-usa DOT com>
Subject: Re: nm for .exe extensions?
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u57FhcwX028265

Warren Young-2 wrote
> On May 24, 2016, at 6:43 AM, Benjamin Cao &lt;

> becao@

> &gt; 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 ?




--
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
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple