Re: Port binding under linux in ASM
- From: tin.cans.and.string@xxxxxxxxx
- Date: Sat, 19 Apr 2008 21:38:40 -0700 (PDT)
On Apr 19, 4:53 pm, tin.cans.and.str...@xxxxxxxxx wrote:
Actually, disregard, please - found the generic include file on your
website. This is good stuff. Thank you!
Chuck:
You've been extremely helpful, and I appreciate it. I *thought* I
understood what p0, p1, and p2 were, but it's becoming increasingly
apparent with every failure that I don't yet get it.
It looks very much to me like these are the placeholders for the
parameters which would be passed in C to 'socket()' while creating the
fd, as in 'socketfd = socket(PF_INET, SOCK_STREAM, 0);', so I assumed
we were dealing with a stack frame, at first, but that didn't do the
job. Seeing as they're not explicitly pointed to by any register at
the time of the syscall, I couldn't see that there was much use
specifically defining them as data.
If you're of the inclination to elaborate on the nature of p0-p2, I'd
be very grateful. Thanks for all your help.
.
- Follow-Ups:
- Re: Port binding under linux in ASM
- From: Chuck Crayne
- Re: Port binding under linux in ASM
- References:
- Port binding under linux in ASM
- From: tin . cans . and . string
- Re: Port binding under linux in ASM
- From: Chuck Crayne
- Re: Port binding under linux in ASM
- From: tin . cans . and . string
- Re: Port binding under linux in ASM
- From: tin . cans . and . string
- Port binding under linux in ASM
- Prev by Date: Re: Port binding under linux in ASM
- Next by Date: Re: Port binding under linux in ASM
- Previous by thread: Re: Port binding under linux in ASM
- Next by thread: Re: Port binding under linux in ASM
- Index(es):
Relevant Pages
|