From: "Smith, Jonathan C5" <SmithJC5@navair.navy.mil>
To: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: RE: PR 207, 662
Date: Tue, 29 Oct 2002 11:44:00 -0000 [thread overview]
Message-ID: <F97EA20B113CD211A6C40000F81EE1F10ED008D3@nems07.nawcad.navy.mil> (raw)
Further investigation has reduced this problem to binaries linked against
libpthread. A simple cout "Hello world" should work when not linked against
libpthread, then fail when linked against it.
I hope this helps.....
Jonathan Smith
-----Original Message-----
From: Andrew Cagney [mailto:ac131313@redhat.com]
Sent: Wednesday, October 23, 2002 5:00 PM
To: Smith, Jonathan C5
Cc: 'gdb@sources.redhat.com'
Subject: Re: PR 207, 662
> Snapshot from 20020403, 5.2.0, 5.2.1.
>
> I haven't taken a snapshot from the 5.3 branch as it takes a few hours to
> transfer to the stand-alone network. I shall do that tonight. Is there a
> reason to expect this fixed in the latest snapshot when its been a problem
> for a long time (PR 207 is dated Tue Sep 04 09:18:01 PDT 2001) and I don't
> see any resolution information in the PRs.
A month or so back MichaelS KevinB and I gave the MIPS on IRIX stuff a
``good talking too', n32, n64 and o32 now work a lot better. It was all
on 6.5 with the IRIX compiler, from memory 207 refers to 5.x.
Andrew
next reply other threads:[~2002-10-29 19:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 11:44 Smith, Jonathan C5 [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-18 5:32 Smith, Jonathan C5
2002-11-19 14:31 ` Andrew Cagney
2002-11-18 4:55 Smith, Jonathan C5
2002-11-19 14:29 ` Andrew Cagney
2002-10-24 8:43 Smith, Jonathan C5
2002-11-15 17:18 ` Andrew Cagney
2002-10-23 13:36 Smith, Jonathan C5
2002-10-23 14:30 ` Andrew Cagney
2002-10-23 11:12 Smith, Jonathan C5
2002-10-23 11:45 ` Andrew Cagney
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=F97EA20B113CD211A6C40000F81EE1F10ED008D3@nems07.nawcad.navy.mil \
--to=smithjc5@navair.navy.mil \
--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