This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GDB locks up -- Cannot find new threads: generic error

From: Andreas Schwab <schwab at suse dot de>
To: David Lecomber <david at allinea dot com>
Cc: gdb <gdb at sources dot redhat dot com>
Date: Thu, 28 Apr 2005 01:33:17 +0200
Subject: Re: GDB locks up -- Cannot find new threads: generic error
References: <1114627357.31720.81.camel@cpc4-oxfd5-5-0-cust111.oxfd.cable.ntl.com><20050427190108.GA28978@nevyn.them.org> <jefyxbvnwd.fsf@sykes.suse.de><20050427225101.GA32735@nevyn.them.org>

Daniel Jacobowitz <drow@false.org> writes:

> That's quite possible; thank you for the information.  Maybe we can
> improve the test to detect the problem more easily.  Any suggestions?

That should be easy to detect, the broken kernels will store 64bit value
through the pointer passed to ptrace GETEVENTMSG.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

References:
- GDB locks up -- Cannot find new threads: generic error
  - From: David Lecomber
- Re: GDB locks up -- Cannot find new threads: generic error
  - From: Daniel Jacobowitz
- Re: GDB locks up -- Cannot find new threads: generic error
  - From: Andreas Schwab
- Re: GDB locks up -- Cannot find new threads: generic error
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]