From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13980 invoked by alias); 3 Dec 2001 05:28:05 -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 13958 invoked from network); 3 Dec 2001 05:28:02 -0000 Received: from unknown (HELO localhost.cygnus.com) (24.114.42.213) by sources.redhat.com with SMTP; 3 Dec 2001 05:28:02 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id 81AC03D59; Mon, 3 Dec 2001 00:28:02 -0500 (EST) Message-ID: <3C0B0D62.3040708@cygnus.com> Date: Sun, 02 Dec 2001 21:28:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.3) Gecko/20011020 X-Accept-Language: en-us MIME-Version: 1.0 To: David Relson Cc: 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> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2001-12/txt/msg00007.txt.bz2 > 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. sigh, Andrew