Date: Thu, 27 Jun 2002 21:42:41 +0200 From: Szilveszter Adam <sziszi@bsd.hu> To: freebsd-current@FreeBSD.ORG Subject: Re: interesting: problem with nm? Message-ID: <20020627194240.GB688@fonix.adamsfamily.xx> In-Reply-To: <20020627121338.A20455@FreeBSD.ORG> References: <200206271445.g5REjCY1015495@bunrab.catwhisker.org> <200206271728.g5RHS0Yl041759@apollo.backplane.com> <20020627180520.GC561@unixpages.org> <20020627182346.GA688@fonix.adamsfamily.xx> <20020627121338.A20455@FreeBSD.ORG>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 27, 2002 at 12:13:39PM -0700, Juli Mallett wrote: > If no file is specified for nm to operate on it operates on a.out by default > like most other programs that deal with binaries. > > If a.out does not exist, then you will indeed see that. Thanks for the clarification, I expected it to print a version string (because I was only interested in seeing that it does not die after the pmap fix) but had to find out from the man page, that nm(1) uses -V for that, while all other members of the binutils family opt for -v. Oh well... Consistency in software design rocks. So, problem solved. Thanks to all who responded. -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020627194240.GB688>