From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6569 invoked by alias); 3 Dec 2001 15:49:11 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6548 invoked from network); 3 Dec 2001 15:49:10 -0000 Received: from unknown (HELO halden.devel.redhat.com) (199.183.24.200) by sources.redhat.com with SMTP; 3 Dec 2001 15:49:10 -0000 Received: (from teg@localhost) by halden.devel.redhat.com (8.11.6/8.11.6) id fB3Fn5V14069; Mon, 3 Dec 2001 10:49:05 -0500 X-Authentication-Warning: halden.devel.redhat.com: teg set sender to teg@redhat.com using -f To: Andrew Cagney Cc: David Relson , gdb@sources.redhat.com Subject: Re: Problem with threaded program References: <3C0A7599.3040902@cygnus.com> <4.3.2.7.2.20011202114313.00c40ab0@mail.osagesoftware.com> <3C0A7599.3040902@cygnus.com> <4.3.2.7.2.20011202201853.00bfba30@mail.osagesoftware.com> <3C0B0D62.3040708@cygnus.com> Organization: Red Hat, Inc. From: teg@redhat.com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) Date: Mon, 03 Dec 2001 07:49:00 -0000 In-Reply-To: <3C0B0D62.3040708@cygnus.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-SW-Source: 2001-12/txt/msg00010.txt.bz2 Andrew Cagney writes: > > Daniel, > > I don't know what the division of labor is between gdb and the > > kernel for situations like this, so I can't comment on that. I can > > report, however, that the problem doesn't occur with gdb-4.18. I > > had previously tested with an old copy of gdb-4.18. To remove one > > possible difference, I have tested for the problem using copies of > > both gdb-4.18 and gdb-5.1 built today under the 2.4.16 kernel. > > gdb-4.18 works properly and gdb-5.1 shows the problem. If the > > problem is in the kernel, then 4.18 and 5.1 must be using different > > capabilities ... > > > > Yes, very, very different: > > >> The apparent 4.18 -> 5.0 ``breakage'' would have occured because GDB > >> switched to using the thread-db/kernel interface. > > best way to describe this is, unfortunatly, is ``radical > surgery''. While the new implementation is significantly better and > definitly worth the effort. however, it is showing up a few teathing > problems. Just make certain that your kernel/glibc are recent. Doesn't help in this case. -- Trond Eivind Glomsrød Red Hat, Inc.