Date: Sat, 6 Mar 2004 16:04:55 +0000 From: chungwei Hsiung <chsiung2@buffalo.edu> To: des@des.no (Dag-Erling =?ISO-8859-1?Q?Sm=F8rgrav?=) Cc: freebsd-hackers@freebsd.org Subject: Re: Strange instructions in compiler output Message-ID: <20040306160455.0d3f5c76@bear.bflony.adelphia.net> In-Reply-To: <xzpeks5u2i9.fsf@dwp.des.no> References: <4048CA38.6040203@yahoo.com> <20040305233209.GO67801@wantadilla.lemis.com> <20040306142651.314430be@bear.bflony.adelphia.net> <20040306202517.GA8384@x-anthony.com> <xzpllmdu37s.fsf@dwp.des.no> <20040306154404.7da5ba81@bear.bflony.adelphia.net> <xzpeks5u2i9.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
OH.... yes... this is FreeBSD not linux, I will try it on the linux box later thank you for the clarification, but how does FreeBSD know where the passed arguments are?? just out of curiosity.. thanks again Chungwei On Sat, 06 Mar 2004 21:47:10 +0100 des@des.no (Dag-Erling Smørgrav) wrote: > chungwei Hsiung <chsiung2@buffalo.edu> writes: > > I still don't understand it because we are supposed to pass in the > > op code 0xb to %eax, and arguments to %ebx, %ecx, and %edx before > > calling interupt, but I can't see any of those instruction > > anywhere. Did I miss anything? > > Huh? Arguments are passed on the stack, and execve() is syscall 59 > (0x3b as you can see in the disassembly). What gave you the idea that > we were passing arguments in registers? This isn't DOS, you know... > > DES > -- > Dag-Erling Smørgrav - des@des.no >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040306160455.0d3f5c76>