Please use group reply, so that you do not drop the bug tracking system
from CC.
On Mon, Dec 19, 2005 at 10:28:23AM -0500, Gene Cooperman wrote:
> I'd like to repeat this in my own words, to see if I understand your point.
> You seem to be saying that:
> A. The parent process begins with the user'
On Mon, Dec 19, 2005 at 01:54:52AM -0500, Gene Cooperman wrote:
> Perhaps my description was not clear enough, but this would be a very
> strange feature. When setrlimit() is called in the original process
> as specified, then after that, pthread_create() continues to succeed
> in the original pro
On Sun, Dec 18, 2005 at 04:31:52AM -0500, Gene Cooperman wrote:
> The details of the bug are in BUG-glibc/README in the tarball. In brief,
> using setrlimit on RLIM_STACK, I set rlim_max to RLIM_INFINITY and rlim_cur
> to something unnaturally high (e.g. 2 GB). I then call
> system("./pthread"),
Package: libc6
Version: 2.3.5-8
I'd like to report a bug in glibc (or possibly its interaction
with the Linux kernel). I have verified the bug both on Debian
and on Scientific Linux (derived from Red Hat). The bug can be
reproduced using the attached tarball:
tar zxvf BUG-glibc.tar.gz
cd BUG
4 matches
Mail list logo
