From: Harry Kalogirou <harkal@gmx.net>
To: Harry Kalogirou <harkal@gmx.net>
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: bug with vfork, execv
Date: 02 Nov 2002 00:26:34 +0200 [thread overview]
Message-ID: <1036189593.16097.77.camel@cool> (raw)
In-Reply-To: <1036181894.16096.60.camel@cool>
> Hi all,
> now that the kernel supports a growing stack I was able to observe an
^
I mean heap here --------------------------
> bug concering vfork and the way libc finds the current heap ending
> point(brk).
prev parent reply other threads:[~2002-11-01 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 20:19 bug with vfork, execv Harry Kalogirou
2002-11-01 22:26 ` Harry Kalogirou [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1036189593.16097.77.camel@cool \
--to=harkal@gmx.net \
--cc=linux-8086@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.