On Wed, May 28, 2003 at 02:34:50PM +0300, Nir Livni wrote: > Now I know for sure that the child crashes (SIGSEGV) before fork() returns. > I could see it in the UML debugger. > It does not use the signal handler I have set up of the SIGSEGV. It simply > crashes and exits. > > Could this be any kernel problem ? It could. Though I would expect kernel to print an OOPS message if it fails in a way like this. I expect it happens in some specific situation. Perhaps you should post little more details about it. > > > > > > Hi all, > > I am experiencing a problem, where fork() returns succesfully > > on parent, but does not return on child. The child process > > simply "disappears". I believe it might have got a SIGSEGV > > (if it makes any sence) before fork() has returned. > > > > I would like to track down this problem. > > What I did so far is: > > 1. I tried first to make sure there are no memory overruns > > using few tools. 2. I tried to look at strace output, but the > > problem does not occur if I use strace 3. I made a > > UserModeLinux machine and now I would like to breakpoint the > > created child before it crashes (assuming it really crashes) > > > > How do I do that ? > > > > Thanks, > > Nir > > > > -- > > Kernelnewbies: Help each other learn about the Linux kernel. > > Archive: http://mail.nl.linux.org/kernelnewbies/ > > FAQ: http://kernelnewbies.org/faq/ > > > -- > Kernelnewbies: Help each other learn about the Linux kernel. > Archive: http://mail.nl.linux.org/kernelnewbies/ > FAQ: http://kernelnewbies.org/faq/ > ------------------------------------------------------------------------------- Jan 'Bulb' Hudec <bulb@ucw.cz> -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
