From owner-freebsd-questions Fri Nov 26 11: 3:15 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 58C361510F; Fri, 26 Nov 1999 11:03:08 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991126140306.21678@mojave.sitaranetworks.com> Date: Fri, 26 Nov 1999 14:03:06 -0500 From: Greg Lehey To: Marc Tardif , freebsd-hackers@FreeBSD.ORG Subject: Re: disassembling syscalls Reply-To: Greg Lehey References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Marc Tardif on Fri, Nov 26, 1999 at 01:51:50PM -0500 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [removing -questions; this is a technical question] On Friday, 26 November 1999 at 13:51:50 -0500, Marc Tardif wrote: > How can syscalls be disassembled on BSD? > > So far, I tried using ktrace -tc on compiled code using the syscall I > wanted, but the output from kdump doesn't look like asm. I also tried > using gdb directly, compiling the source with the -g and -static flags, > but I couldn't use the disassemble command on the syscall which appeared > in the output of 'disassemble main'. I'm not sure what you want to do here. Use a debugger for disassembly. But what do you really want to do? And what do you mean by 'syscall'? The userland stub function, the interface, or the kernel code which implements the call? In any case, since we have the source code to all of it, it's not clear that there's much to be gained by disassembling them. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message