On Tuesday, 29 June 1999 at 5:56:37 -0400, Brian F. Feldman wrote:
> On Tue, 29 Jun 1999, Brian F. Feldman wrote:
>
>>
>> That's not true, Greg. I'm sure you of all people know that it (the
>> composition of address space) is described in "The Design and
>> Implementation of the 4.4BSD Operating
On Tuesday, 29 June 1999 at 5:56:37 -0400, Brian F. Feldman wrote:
> On Tue, 29 Jun 1999, Brian F. Feldman wrote:
>
>>
>> That's not true, Greg. I'm sure you of all people know that it (the
>> composition of address space) is described in "The Design and
>> Implementation of the 4.4BSD Operating S
Wes Peters <[EMAIL PROTECTED]> wrote:
>Time for a main() man page? Where would it go? Section 2, 3, or 9?
>Hmm...
I'd support that. I believe the page needs to be tied to exec (ala
setjmp/longjmp), which means it either ties to execve(2) or exec*(3).
Note that execve(2) already includes a ref
Wes Peters wrote:
>Time for a main() man page? Where would it go? Section 2, 3, or 9?
>Hmm...
I'd support that. I believe the page needs to be tied to exec (ala
setjmp/longjmp), which means it either ties to execve(2) or exec*(3).
Note that execve(2) already includes a reference to the callin
On Tue, 29 Jun 1999, Brian F. Feldman wrote:
>
> That's not true, Greg. I'm sure you of all people know that it (the
> composition of address space) is described in "The Design and
> Implementation of the 4.4BSD Operating System," even if things
> are slightly different in FreeBSD of today (espe
On Tue, 29 Jun 1999, Brian F. Feldman wrote:
>
> That's not true, Greg. I'm sure you of all people know that it (the
> composition of address space) is described in "The Design and
> Implementation of the 4.4BSD Operating System," even if things
> are slightly different in FreeBSD of today (espec
On Tuesday, 29 June 1999 at 5:49:04 -0400, Brian F. Feldman wrote:
> On Tue, 29 Jun 1999, Greg Lehey wrote:
>
>> On Monday, 28 June 1999 at 23:32:59 -0400, Amol Mohite wrote:
>>> What I want to know is the exact position of these variables on the stack.
>>
>> As I said, at the top.
>>
>>> and if
On Tuesday, 29 June 1999 at 5:49:04 -0400, Brian F. Feldman wrote:
> On Tue, 29 Jun 1999, Greg Lehey wrote:
>
>> On Monday, 28 June 1999 at 23:32:59 -0400, Amol Mohite wrote:
>>> What I want to know is the exact position of these variables on the stack.
>>
>> As I said, at the top.
>>
>>> and if a
On Tue, 29 Jun 1999, Greg Lehey wrote:
> On Monday, 28 June 1999 at 23:32:59 -0400, Amol Mohite wrote:
> > What I want to know is the exact position of these variables on the stack.
>
> As I said, at the top.
>
> > and if anywhere I can find some data, on the exact compisoition of
> > the stcak
On Tue, 29 Jun 1999, Greg Lehey wrote:
> On Monday, 28 June 1999 at 23:32:59 -0400, Amol Mohite wrote:
> > What I want to know is the exact position of these variables on the stack.
>
> As I said, at the top.
>
> > and if anywhere I can find some data, on the exact compisoition of
> > the stcak,
Greg Lehey wrote:
>
> On Tuesday, 29 June 1999 at 12:18:07 +1000, Patryk Zadarnowski wrote:
> >
> > This is of course correct except for the `undocumented' claim. The
> > `envp' has been documented as the third argument to main() since the
> > Pharaons (well, not quite ;). Apparently AT&T UNIX ev
Greg Lehey wrote:
>
> On Tuesday, 29 June 1999 at 12:18:07 +1000, Patryk Zadarnowski wrote:
> >
> > This is of course correct except for the `undocumented' claim. The
> > `envp' has been documented as the third argument to main() since the
> > Pharaons (well, not quite ;). Apparently AT&T UNIX eve
e address space)
>
> struct kframe {
> int argc; /* "argc" to be passed to main() */
> char *argv[argc]; /* "argv" to be passed to main() */
> char *null; /* a NULL pointer terminating argv[] */
>
e address space)
>
> struct kframe {
> int argc; /* "argc" to be passed to main() */
> char *argv[argc]; /* "argv" to be passed to main() */
> char *null; /* a NULL pointer terminating argv[] */
>
> I know about envp.
>
> What I want to know is the exact position of these variables on the stack.
>
> and if anywhere I can find some data, on the exact compisoition of the
> stcak, then it will be very helpful.
>
> references of books and websites wil be most helpful.
Basically, i386 BSD k
> I know about envp.
>
> What I want to know is the exact position of these variables on the stack.
>
> and if anywhere I can find some data, on the exact compisoition of the
> stcak, then it will be very helpful.
>
> references of books and websites wil be most helpful.
Basically, i386 BSD ke
On Monday, 28 June 1999 at 23:32:59 -0400, Amol Mohite wrote:
>> On Monday, 28 June 1999 at 5:54:29 -0400, Amol Mohite wrote:
>>>
>>> Hi!
>>>
>>> i hope this is the right list for this qs.
>>>
>>> I wanted t know where the environment
On Monday, 28 June 1999 at 23:32:59 -0400, Amol Mohite wrote:
>> On Monday, 28 June 1999 at 5:54:29 -0400, Amol Mohite wrote:
>>>
>>> Hi!
>>>
>>> i hope this is the right list for this qs.
>>>
>>> I wanted t know where the environment
at 5:54:29 -0400, Amol Mohite wrote:
> >
> > Hi!
> >
> > i hope this is the right list for this qs.
> >
> > I wanted t know where the environment strings i bsd were stored after a
> > program execs another one.
>
> At the top of memory. You
at 5:54:29 -0400, Amol Mohite wrote:
> >
> > Hi!
> >
> > i hope this is the right list for this qs.
> >
> > I wanted t know where the environment strings i bsd were stored after a
> > program execs another one.
>
> At the top of memory. You can acce
On Tue, 29 Jun 1999, Greg Lehey wrote:
> > This is of course correct except for the `undocumented' claim. The
> > `envp' has been documented as the third argument to main() since the
> > Pharaons (well, not quite ;). Apparently AT&T UNIX even has a
> > (documented) five-parameter main().
>
> Thi
On Tue, 29 Jun 1999, Greg Lehey wrote:
> > This is of course correct except for the `undocumented' claim. The
> > `envp' has been documented as the third argument to main() since the
> > Pharaons (well, not quite ;). Apparently AT&T UNIX even has a
> > (documented) five-parameter main().
>
> This
> > This is of course correct except for the `undocumented' claim. The
> > `envp' has been documented as the third argument to main() since the
> > Pharaons (well, not quite ;). Apparently AT&T UNIX even has a
> > (documented) five-parameter main().
>
> This is news to me. Can you point to the
> > This is of course correct except for the `undocumented' claim. The
> > `envp' has been documented as the third argument to main() since the
> > Pharaons (well, not quite ;). Apparently AT&T UNIX even has a
> > (documented) five-parameter main().
>
> This is news to me. Can you point to the d
On Tuesday, 29 June 1999 at 12:18:07 +1000, Patryk Zadarnowski wrote:
>
>>> I wanted t know where the environment strings i bsd were stored after a
>>> program execs another one.
>
> extern char **environ;
>
>> At the top of memory. You can access them
On Tuesday, 29 June 1999 at 12:18:07 +1000, Patryk Zadarnowski wrote:
>
>>> I wanted t know where the environment strings i bsd were stored after a
>>> program execs another one.
>
> extern char **environ;
>
>> At the top of memory. You can access them by the s
> > I wanted t know where the environment strings i bsd were stored after a
> > program execs another one.
extern char **environ;
> At the top of memory. You can access them by the standard (but
> undocumented) method:
>
> int main (int argc, char *argv [], char
> > I wanted t know where the environment strings i bsd were stored after a
> > program execs another one.
extern char **environ;
> At the top of memory. You can access them by the standard (but
> undocumented) method:
>
> int main (int argc, char *argv [], char
On Monday, 28 June 1999 at 5:54:29 -0400, Amol Mohite wrote:
>
> Hi!
>
> i hope this is the right list for this qs.
>
> I wanted t know where the environment strings i bsd were stored after a
> program execs another one.
At the top of memory. You can access them
On Monday, 28 June 1999 at 5:54:29 -0400, Amol Mohite wrote:
>
> Hi!
>
> i hope this is the right list for this qs.
>
> I wanted t know where the environment strings i bsd were stored after a
> program execs another one.
At the top of memory. You can access them
Hi!
i hope this is the right list for this qs.
I wanted t know where the environment strings i bsd were stored after a
program execs another one.
Is there any place I ca get hold of the ABIs for freebsd ?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
Hi!
i hope this is the right list for this qs.
I wanted t know where the environment strings i bsd were stored after a
program execs another one.
Is there any place I ca get hold of the ABIs for freebsd ?
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-ha
32 matches
Mail list logo
