From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12949 invoked by alias); 8 Aug 2002 17:34:10 -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 12941 invoked from network); 8 Aug 2002 17:34:10 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 8 Aug 2002 17:34:10 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 87DC13F6E; Thu, 8 Aug 2002 13:34:08 -0400 (EDT) Message-ID: <3D52AB90.4050203@ges.redhat.com> Date: Thu, 08 Aug 2002 10:34:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020802 X-Accept-Language: en-us, en MIME-Version: 1.0 To: bennet Cc: gdb@sources.redhat.com Subject: Re: GDB threading/FP bug References: <14c93f3a.0208071239.2143c199@posting.google.com> <14c93f3a.0208080853.413a3b88@posting.google.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00073.txt.bz2 > Some better searching revealed this is a very old bug. From last > year: > > http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&th=adfbc404c374e980&seekm=OF36816CDD.AE7D54AF-ONC1256B1F.005622DC%40icos.be&frame=off > > I tried running GDB in GDB and I was able to get as far as seeing that > the floats seemed to be pushed onto the stack correctly until the > thread switch and all the ptrace stuff, but I wasn't totally sure if > the bug I was seeing at that point was in the GDB'd GDB or was the > same bug in the outter GDB. [Mailing list changed to something with less spam :-)] As you've discovered, there have been a number of very similar bugs that all involving corrupted FP and threads. It was thought that fixes for all such bugs were incorporated into both 5.2.* (http://sources.redhat.com/gdb/download/) and the mainline (http://sources.redhat.com/gdb/current/). Can you please check that your problem does occur in the latest release/mainline, and if it does, create a bug report using http://sources.redhat.com/gdb/bugs/. enjoy, Andrew