Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> And at some time (when running mach_thread_self several times in threads
> where the above error already happened) the kernel will panic with
> thread_invoke or thread_dispatch. Seems that there is some
> non-robustness in this area.
Have you tried creating a reasonably small test-case that provokes the
error?
IIRC, Roland said that the sequence of messages corresponded to a fork
immediately followed by another fork by the child. Perhaps something
simple like
#include <unistd.h>
int main(int argc, char **argv)
{
if (!fork()) fork();
_exit(0);
}
or
#include <unistd.h>
int main(int argc, char **argv)
{
int i;
for (i = 0; i < 47; i++)
if (fork()) break;
_exit(0);
}
also crashes?
/Niels
_______________________________________________
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
