Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: David Lecomber <david@allinea.com>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: GDB locks up -- Cannot find new threads: generic error
Date: Wed, 27 Apr 2005 22:46:00 -0000	[thread overview]
Message-ID: <20050427190108.GA28978@nevyn.them.org> (raw)
In-Reply-To: <1114627357.31720.81.camel@cpc4-oxfd5-5-0-cust111.oxfd.cable.ntl.com>

On Wed, Apr 27, 2005 at 07:42:37PM +0100, David Lecomber wrote:
> (gdb) b main
> Breakpoint 1 at 0x804ed18: file
> main.cpp, line 10.
> (gdb) run
> Starting program: a.out
> warning: linux_test_for_tracefork: unexpected result from waitpid
> (28261,
> status 0x117f)
> [Thread debugging using libthread_db enabled]
> Error while reading shared library symbols:
> Cannot find new threads: generic error
> 
> at this point GDB does nothing and is unresponsive to any user input.  
> 
> 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.

> - and if it helps,  I turned on debug of  lin-lwp and saw:
> 
> Starting program: ./a.out
> CW: waitpid 28606 received Trace/breakpoint trap (stopped)
> CW: waitpid 28606 received Child exited (stopped)
> CW: waitpid 28606 received Child exited (stopped)
> CW: waitpid 28606 received Child exited (stopped)
> CW: waitpid 28606 received Child exited (stopped)
> CW: waitpid 28606 received Child exited (stopped)
> CW: waitpid 28606 received Child exited (stopped)
> CW: waitpid 28606 received Child exited (stopped)
> CW: waitpid 28606 received Child exited (stopped)
> CW: waitpid 28606 received Child exited (stopped)
> CW: waitpid 28606 received Child exited (stopped)
> CW: waitpid 28606 received Child exited (stopped)
> CW: waitpid 28606 received Child exited (stopped)
> CW: waitpid 28606 received Child exited (stopped)
> CW: waitpid 28606 received Trace/breakpoint trap (stopped)
> warning: linux_test_for_tracefork: unexpected result from waitpid
> (28629,
> status
> 0x117f)
> CW: waitpid 28606 received Trace/breakpoint trap (stopped)
> [Thread debugging using libthread_db enabled]
> Error while reading shared library symbols:
> Cannot find new threads: generic error
> LLR: PTRACE_SINGLESTEP process 28606, 0 (resume event thread)
> LLW: waitpid 28606 received Trace/breakpoint trap (stopped)

So um, if the program has stopped, what does GDB think it's still
waiting for?  Might want to strace gdb (without -f, with -e
wait4,ptrace).

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-04-27 19:01 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 [this message]
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
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=20050427190108.GA28978@nevyn.them.org \
    --to=drow@false.org \
    --cc=david@allinea.com \
    --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