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:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=jptwBUe6RntapJIp3P5jEaH9RpFdrxMBpenqrnw8hLTTFsX0+NznE
	op7j11I1z3aHfYB45tcaVX2o2ZX6qiUfg7OOnqPa/HRWuIwfN75mSt5S3K4KHSRN
	RUqWtvf4OlDSNJ5ORyxKwOuTw392ZLcWm4/5OX/gEnv2fez4LzXbnY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Tue, 7 Jun 2016 18:12:21 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: nm for .exe extensions?
Message-ID: <20160607161221.GD3023@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <a66eaf9339774b6a8fbc1ab4b99f428d@ntmaexbe04.bedford.progress.com> <76282617-B02E-4782-B4A0-AEB3756DE152@etr-usa.com> <1465314195730-127453.post@n5.nabble.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="NKoe5XOeduwbEQHU"
Content-Disposition: inline
In-Reply-To: <1465314195730-127453.post@n5.nabble.com>
User-Agent: Mutt/1.6.1 (2016-04-27)

--NKoe5XOeduwbEQHU
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Jun  7 08:43, Bill Smith wrote:
> Warren Young-2 wrote
> > On May 24, 2016, at 6:43 AM, Benjamin Cao &lt;
>=20
> > becao@
>=20
> > &gt; wrote:
> >>=20
> >> The executable, when run with nm in Cygwin, results in a "no symbols"
> >> result, whereas it generates a symbol table in unix.
> >=20
> > That=E2=80=99s not what I see here.  Given hello.c containing a =E2=80=
=9CHello, world!=E2=80=9D
> > program:
> >=20
> >   $ make hello
> >   cc     hello.c   -o hello
> >   $ nm hello.exe | wc -l
> >   389
> >=20
> > If I strip the exe, I get =E2=80=9CNo symbols,=E2=80=9D as expected.  T=
here=E2=80=99s 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=E2=80=99s an objec=
t file or a
> > DLL.
>=20
> 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.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--NKoe5XOeduwbEQHU
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXVvJlAAoJEPU2Bp2uRE+g9H0QAJBeFsa8xH/8qGJWarMHrLiG
nAAiamx6b4tS8jfkvE0ci1Oc9wu4eosfSxReFMdJzoDHEo2zZ5w652l3TBFYK1kV
+LXs0L332hp3DzIxT1exPCURvpNd/MEsRGWFSiIuiKldxzuAzSADsNJdvLw/sT2z
+VtorpnBRfBOMbj7ACd5wsboGUyYXPzxdFTWdyDswGkrv66OsxPRAGurFOZ9hDfl
6hrwOP2VQ9jjxsx0Eli3rQnkudHvQmeza/9H04WOIBaATYcOHbaL9QmnoNVlh81d
fpAKWn3MRDi+ci4IVHbCzwPSof/RgiZ3jko+sZk9eW9nqcANSqi3KjPSQhqvu2yL
F+qhvCIlhnmzEqAhZAjmqMn66LxO4TlYuVIOr2Qxeu0sxE6oghk68TW4BMzvHv7D
1w8DNXJMVrLzTXIFU3dRqvV0teU5nIf33MK5e4lL2hCp2RO+RyfD5Aek102eezi8
quaIjv0M6mtgW9KjtD1uyCMMKqmP7slRl46kIEj/+YkhMUyJckxAp0h/ww62hz6N
/e2opmZjdzYudGrYCB0xEBLzsdyo25pe2/bojklZIhBLUnHzGqbY4PdCgAHcKUNw
/bdXM9ZkBo1IRdegSuIiLkkTu8pSCPKdcPpIEebBQfuU2e/srfISRPWscRguBbMO
NBOofI6cA/LvH98T86Kt
=UA9M
-----END PGP SIGNATURE-----

--NKoe5XOeduwbEQHU--