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:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type:content-transfer-encoding;
	q=dns; s=default; b=fkkalNWbbcAMKjBP5clE9bac1WLHVtyxaV4UWCV+2KI
	qscdiiTREQcy4OgofIonrMxf7oBPjFuWl3dbNROc3590DMQ/KfkTte0KnrHxDS2A
	cbRSqUCIiukclMknj5AADmeR+bTccga+ksrFMZgY2cydi8eC491d5nDMZBMnrAHs
	=
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:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type:content-transfer-encoding;
	s=default; bh=nMN7P9HpBXIrSCjDgaGvBDbPdlQ=; b=dF4t6+HmCGAELhRem
	mDgOAGQcpRIR4UzN5oFN9/UJYz2X1JuZ6DcGtCpiCJ91Nrc39qcbQ/r8+ZX8wl4k
	UGzsjlKJ0eVVX8znnTStVUNeIzfJslTiUqiy6OUFm71Ham8aqiVpczF1PL913ZUv
	rHr3/4BmKOyXd6RKHbMqw3+Ytg=
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_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=cao, corinnacygwincygwincom, corinna-cygwin AT cygwin DOT com
X-HELO:	mail-wm0-f42.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=ULcslxrMm5RqWSfxvMkKhs0aycQJ+VB7sD2PkKWalgg=; b=RlzS0OriMRL9JYjj92+MfJ+aRl4mtV07ygjOiFe7p2z6a4rSgGukFskCA1IzSSfMge 92EWb0sXSeAsEBwH5g7b6l+I9UKxjZGk63HxEzcGfKVzxItdIK8mRYbXajhYYmXxU5od IZao+G+Ib1fgb8tjBf2XzAeAMnEAaJUMSgjndMJAxG0tpHdb5CumIlh9TGKyWYaNGIyD jNZECSwDxrNGgFPAzvpo0h3EEP+ei5tWqHSCnnXHWYlhu6PYipmwyzKyQ+strh9wece3 UmrG9GhQd1kS07OP5GE/k8yBBI38rCiKlWfyiT1Ba7Vt3hyRilY9H7u3TEmpfQmfAct8 i9bw==
X-Gm-Message-State:	ALyK8tIxf76bUrS8lC4Rq4krOej/KBbbeGYVwuEEMzmq5oJZUqyzGTvc30tjzl8qe3NIxHLlknfY3mvLtoPOxw==
X-Received:	by 10.28.189.130 with SMTP id n124mr3686055wmf.76.1465316634601; Tue, 07 Jun 2016 09:23:54 -0700 (PDT)
MIME-Version:	1.0
In-Reply-To:	<20160607161221.GD3023@calimero.vinschen.de>
References:	<a66eaf9339774b6a8fbc1ab4b99f428d AT ntmaexbe04 DOT bedford DOT progress DOT com> <76282617-B02E-4782-B4A0-AEB3756DE152 AT etr-usa DOT com> <1465314195730-127453 DOT post AT n5 DOT nabble DOT com> <20160607161221 DOT GD3023 AT calimero DOT vinschen DOT de>
From:	Ismail Donmez <ismail AT i10z DOT com>
Date:	Tue, 7 Jun 2016 19:23:24 +0300
Message-ID:	<CAFo71_6UOvDv2eNRWVix96iJDXw3+bXg1CxoMe-WRxFy8+aXyQ@mail.gmail.com>
Subject:	Re: nm for .exe extensions?
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id u57GOKWa032180

Hi,

On Tue, Jun 7, 2016 at 7:12 PM, Corinna Vinschen
<corinna-cygwin AT cygwin DOT com> wrote:
> On Jun  7 08:43, Bill Smith wrote:
>> 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 ?
>
> 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

ismail

--
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

- Raw text -