From: Nir Livni <nir_l3@netvision.net.il>
To: Anand K <anand_km@hotmail.com>, linux-kernel@vger.kernel.org
Subject: Re: fork() returns on parent but not returns on child
Date: Wed, 28 May 2003 11:08:53 +0200 [thread overview]
Message-ID: <016d01c324f8$c2bde4e0$68d0da51@pinguin> (raw)
In-Reply-To: <BAY1-DAV41oV1qdiixj00001dbc@hotmail.com>
> How about setting up a signal handler? Makes things simpler.
Parent already has a signal handler.
Child does not reach it. It simply exists.
>
> -- Anand K.
> ----- Original Message -----
> From: "Nir Livni" <nir_l3@netvision.net.il>
> Newsgroups: mailinglists.external.linux-kernel
> To: <linux-kernel@vger.kernel.org>
> Cc: "Nir Livni" <nirl@cyber-ark.com>
> Sent: Wednesday, May 28, 2003 4:18 AM
> Subject: fork() returns on parent but not returns on child
>
>
> > 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 make 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
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
prev parent reply other threads:[~2003-05-28 7:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 0:00 Nir Livni
[not found] ` <BAY1-DAV41oV1qdiixj00001dbc@hotmail.com>
2003-05-28 9:08 ` Nir Livni [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='016d01c324f8$c2bde4e0$68d0da51@pinguin' \
--to=nir_l3@netvision.net.il \
--cc=anand_km@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nirl@cyber-ark.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®