From owner-freebsd-hackers Sun Jun 25 9: 2:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id CFE9437B81C for ; Sun, 25 Jun 2000 09:02:17 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id MAA26623; Sun, 25 Jun 2000 12:00:41 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Sun, 25 Jun 2000 12:00:40 -0400 (EDT) From: Chuck Robey To: Warner Losh Cc: FreeBSD Hackers List Subject: Re: disassembling In-Reply-To: <200006250752.BAA09841@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Jun 2000, Warner Losh wrote: > In message Chuck Robey writes: > : Is there any tools whatever (free or commercial) that does disassembly on > : FreeBSD obj's AND will show you the C line and the code that the C line > : caused to be assembled? > > Yes. man objdump. Thanks (also to Boris Popov), I didn't realize objdump would do that. I'd used disassembly before, with line number, but I hadn't seen that -S option. Just what I needed. > > Warner > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message