Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Lecomber <david@allinea.com>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: GDB locks up -- Cannot find new threads: generic error
Date: Tue, 03 May 2005 14:25:00 -0000	[thread overview]
Message-ID: <1115130086.1638.27.camel@delmo.priv.wark.uk.streamline-computing.com> (raw)
In-Reply-To: <jefyxbvnwd.fsf@sykes.suse.de>

> >> The  system is:
> >> kernel-2.4.21-27.EL
> >> glibc-2.3.2-95.30
> >
> > At a guess, your kernel is buggered.  You really should never see that
> > warning.  The unexpected signal is SIGCHLD; your kernel has accepted
> > the SETOPTIONS but obviously failed to stop when the test thread
> > vforked.
> 
> I think that can happen when the 32 bit ptrace emulation is incomplete,
> especially if PTRACE_GETEVENTMSG is not properly emulated.  That should be
> fixed in recent (< 9 months) kernels.

Hello Andreas,

I can reproduce this on a SuSE Opteron machine - running 2.6.8-24.13 -
and 2.6.8 came out 13th August (?).  How - other than brokenness - can I
test if this PTRACE_GETEVENTMSG is the problem?

Regards
David





  parent reply	other threads:[~2005-05-03 14:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-27 19:01 David Lecomber
2005-04-27 22:46 ` Daniel Jacobowitz
2005-04-27 22:51   ` Andreas Schwab
2005-04-27 23:33     ` Daniel Jacobowitz
2005-04-28  1:05       ` Andreas Schwab
2005-05-03 14:25     ` David Lecomber [this message]
2005-05-03 14:48       ` Daniel Jacobowitz
2005-05-03 20:53         ` David Lecomber
2005-05-03 20:55           ` Daniel Jacobowitz
2005-05-03 21:10             ` David Lecomber
2005-05-03 21:14               ` Daniel Jacobowitz
2005-05-03 23:26                 ` David Lecomber

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=1115130086.1638.27.camel@delmo.priv.wark.uk.streamline-computing.com \
    --to=david@allinea.com \
    --cc=gdb@sources.redhat.com \
    --cc=schwab@suse.de \
    /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