From: Wimmer Andreas <andreas.wimmer@joanneum.at>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: follow-fork-mode child on SuSE 9.2 (i586 and x86_64) not working
Date: Thu, 19 May 2005 15:57:00 -0000 [thread overview]
Message-ID: <1116518244.14878.3.camel@dibw112.joanneum.at> (raw)
In-Reply-To: <20050519142215.GA18281@nevyn.them.org>
On Thu, 2005-05-19 at 10:22 -0400, Daniel Jacobowitz wrote:
> On Thu, May 19, 2005 at 03:54:40PM +0200, Wimmer Andreas wrote:
> > Hi,
> > I am using SuSE 9.2 both on i586 and x86_64 platforms and have some
> > troubles to get the follow-fork-mode=child feature working
> > The system is using the kernels provided by the distribution
> > 2.6.8-11.24 (based on 2.6.8 ?)
> > I tried with the distribution provided gdb (6.2.1) and also with 6.3
> > all with the same effect.
> > *) A debugged program starts up normally untill it reaches a fork
> > statement
> > *) The child process is created the debugger detects the child and
> > gives the message "Attaching after fork to child process .."
> > *) The child runs a while (it executed some of the initial code after
> > the fork) and then blocks
> > *) After that GDB also blocks without any chance to do something
> >
> > NOTE: the parent process is left in "S+" state and the child remains in
> > "T+" state.
>
> Can you reproduce this without using a SuSE kernel? If not, you may
> want to report this to SuSE.
Yes I can reproduce this on a a vanilla 2.6.11.10 kernel which I just
compiled for testing.
Same situation, gdb and child process are blocked, without any further
debugging possible.
---------------------
Andreas Wimmer
Joanneum Research
next prev parent reply other threads:[~2005-05-19 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 13:58 Wimmer Andreas
2005-05-19 14:32 ` Daniel Jacobowitz
2005-05-19 15:57 ` Wimmer Andreas [this message]
2005-05-19 15:58 ` Daniel Jacobowitz
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=1116518244.14878.3.camel@dibw112.joanneum.at \
--to=andreas.wimmer@joanneum.at \
--cc=drow@false.org \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).