From: Daniel Jacobowitz <drow@false.org>
To: David Lecomber <david@allinea.com>
Cc: Andreas Schwab <schwab@suse.de>, gdb <gdb@sources.redhat.com>
Subject: Re: GDB locks up -- Cannot find new threads: generic error
Date: Tue, 03 May 2005 20:55:00 -0000 [thread overview]
Message-ID: <20050503205522.GA7648@nevyn.them.org> (raw)
In-Reply-To: <1115153724.10279.13.camel@cpc4-oxfd5-5-0-cust111.oxfd.cable.ntl.com>
On Tue, May 03, 2005 at 09:55:23PM +0100, David Lecomber wrote:
>
> Sorry Dan, it didn't work:
>
> (gdb) b main
> Breakpoint 1 at 0x80484dd: file foo.c, line 15.
> (gdb) r
> Starting program: /users/david/a.out
> warning: linux_test_for_tracefork: Needed to use long, but second half
> was clobbered
Well, that's something - Andreas was right about your kernel having
this broken. The patch may be a good idea anyway to prevent really odd
stack corruption bugs.
> Failed to read a valid object file image from memory.
> [Thread debugging using libthread_db enabled]
> Error while reading shared library symbols:
> Cannot find new threads: generic error
>
>
> followed by hanging..
I will need more information to help you. Useful things: strace of
gdb, backtrace at the time of the hang, whatever else you can think of
to try...
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-03 20:55 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
2005-05-03 14:48 ` Daniel Jacobowitz
2005-05-03 20:53 ` David Lecomber
2005-05-03 20:55 ` Daniel Jacobowitz [this message]
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=20050503205522.GA7648@nevyn.them.org \
--to=drow@false.org \
--cc=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