On Sun, Jan 28, 2001 at 08:22:12PM -0500, Roland McGrath wrote:
> Oh, well, I just now actually looked at your script and realized that you
> are running a fork bomb.
Yep, that seems to be a different bug than the one Neal sees after long
compiles.
Marcus
--
`Rhubarb is no Egyptian god.' Debia
Oh, well, I just now actually looked at your script and realized that you
are running a fork bomb. Which is to say, the essence of that program is
the same as "while (fork () == 0) ;". Such a program always ends in a
pathological resource shortage. Unix has things like per-owner (uid)
resource
That location is inside the allocator, so just from the PC we don't know
what kind of thing is being allocated. We need to see backtrace from the
panic. If ddb works these days, you can use that and then put the PC
values through addr2line.
I just checked in a simple change to zalloc.c to mak
Hi,
we reproduced this by a simple self invoking script
# cat > /tmp/foo
#! /bin/sh
sh /tmp/foo
^D
# sh /tmp/foo
panic: zalloc4
(we changed the panic messages in kern/zalloc.c, zalloc4 is in line 486
(zget_space returns 0)).
Kernel Breakpoint trap, eip 0x10ccc8
Stopped at 0x10ccc7: int $3
tr
