Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@kealia.com>
To: gdb <gdb@sources.redhat.com>
Subject: Re: GDB regressions
Date: Sat, 15 Nov 2003 17:37:00 -0000	[thread overview]
Message-ID: <yf2znexzg75.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20031114221540.GA17634@nevyn.them.org> (Daniel Jacobowitz's message of "Fri, 14 Nov 2003 17:15:41 -0500")

On Fri, 14 Nov 2003 17:15:41 -0500, Daniel Jacobowitz <drow@mvista.com> said:
> On Fri, Nov 14, 2003 at 02:11:48PM -0800, David Carlton wrote:
>> On Fri, 14 Nov 2003 16:57:02 -0500, Daniel Jacobowitz <drow@mvista.com> said:

>>> Why's it doing that?  Has anything else on your system changed
>>> since you last ran the testsuite?

>> The only thing I can think of is that I installed new versions of
>> the glibc RPMs (and installed the glibc-debug rpm, which I hadn't
>> had at all before, but that goes in a directory that isn't in my
>> LD_LIBRARY_PATH).  So it could be a bug in them, I suppose.

> Most likely that's it.  Thread debugging is not working at all if
> you see that message.

Yeah, that's it.  I can't retry on the computer in question (I'm in
the middle of a botched RH8->9 upgrade on it - why can't RH9 find my
external monitor?), but I just tried on my home machine, where I have
the new glibc but haven't done a CVS update on my GDB directory for a
while, and I'm seeing similar issues there.

Sorry for the false alarm.

David Carlton
carlton@kealia.com


  reply	other threads:[~2003-11-15 17:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14 21:37 David Carlton
2003-11-14 21:41 ` David Carlton
2003-11-14 21:57 ` Daniel Jacobowitz
2003-11-14 22:11   ` David Carlton
2003-11-14 22:16     ` Daniel Jacobowitz
2003-11-15 17:37       ` David Carlton [this message]
2003-11-15 14:07     ` Mark Kettenis
2003-11-15  4:46 Michael Elizabeth Chastain
2003-11-16 15:33 Michael Elizabeth Chastain

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=yf2znexzg75.fsf@hawaii.kealia.com \
    --to=carlton@kealia.com \
    --cc=gdb@sources.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