Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "bennet brauer" <bennetbrauer@hotmail.com>
To: kevinb@redhat.com, ac131313@ges.redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: GDB threading/FP bug
Date: Tue, 13 Aug 2002 13:11:00 -0000	[thread overview]
Message-ID: <F91FCGp33khCFQGKpRm000034a5@hotmail.com> (raw)

Well I'm unable to compile from the head of CVS.  I get the following error 
as it tries to compile "po"...  This error doesn't exist in 5.2.1.

file=./`echo fr | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH no -o $file fr.po
/bin/sh: no: command not found


I did however find an old, closed, GDB bug that indicated linux 2.2.19 did 
not have this bug.  And indeed, on a 2.2.19 box, GDB doesn't exhibit this 
bug with my test program.  Currently I'm working around the issue with a 
dummy floating point operation at the top of my program.


>From: Kevin Buettner <kevinb@redhat.com>
>To: Andrew Cagney <ac131313@ges.redhat.com>, bennet 
><bennetbrauer@hotmail.com>
>CC: gdb@sources.redhat.com
>Subject: Re: GDB threading/FP bug
>Date: Thu, 8 Aug 2002 11:36:59 -0700
>
>On Aug 8,  1:34pm, Andrew Cagney wrote:
>
> > > 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/.
>
>Yes, I thought this bug was fixed too.
>
>FWIW, I just did a build of gdb-5.2.1 on a Red Hat 7.3 machine (x86).
>I wasn't able to reproduce the bug using the test program provided by
>Bennet.  (I've also tested the current development sources and, as
>expected, don't see the bug there either.)
>
>Kevin




_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx


             reply	other threads:[~2002-08-13 20:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-13 13:11 bennet brauer [this message]
2002-08-13 13:14 ` Daniel Jacobowitz
     [not found] <14c93f3a.0208071239.2143c199@posting.google.com>
     [not found] ` <14c93f3a.0208080853.413a3b88@posting.google.com>
2002-08-08 10:34   ` Andrew Cagney
2002-08-08 11:37     ` Kevin Buettner

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=F91FCGp33khCFQGKpRm000034a5@hotmail.com \
    --to=bennetbrauer@hotmail.com \
    --cc=ac131313@ges.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=kevinb@redhat.com \
    /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