From: Paul Gilliam <pgilliam@us.ibm.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Did the fix for recycled thread ids uncover another bug?
Date: Tue, 15 Jun 2004 20:29:00 -0000 [thread overview]
Message-ID: <200406151327.31000.pgilliam@us.ibm.com> (raw)
In-Reply-To: <200406151059.59807.pgilliam@us.ibm.com>
Michael,
I am having trouble posting to the mailing list. Or maybe it's any outgoing
mail I'm having problems with. I hope you get this.
On Tuesday 15 June 2004 10:59, Paul Gilliam wrote:
> On Monday 14 June 2004 16:22, Daniel Jacobowitz wrote:
> > On Mon, Jun 14, 2004 at 04:17:47PM -0700, Paul Gilliam wrote:
> > > I will post a follow-up with the details if someone tells me this is
> > > the right mail-list.
> >
> > I already did...
>
> I have done some more homework and found that the problem is with 6.1 and
> seems to be fixed in 6.1.0.90_2004-06-15-cvs (I just tried it). This is
> all on the PowerPC.
>
> So now I need to find a patch for 6.1 that will fix this.
>
> I have attached four files: the first is the test case, tbug.c; two are
> transcripts from gdb 6.1 (with some back-porting) for ppc-32 and for
> ppc-64; the last is a transcript from gdb 6.1.0.90_2004-06-15-cvs for
> ppc-32..
>
> 'tbug' starts two threads, each using the same thread function which just
> waits a few seconds and returns. Set a break-point in 'tf' (the thread
> function) and run. In the 64-bit case, everything works as expected. In
> the 32 bit case, we get a message 'reading register pc (#64): No such
> process' and then we're hosed.
>
> Thanks for any help,
>
> -=# Paul Gilliam #=-
prev parent reply other threads:[~2004-06-15 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 23:17 Paul Gilliam
2004-06-14 23:22 ` Daniel Jacobowitz
2004-06-15 18:01 ` Paul Gilliam
2004-06-15 20:29 ` Paul Gilliam [this message]
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=200406151327.31000.pgilliam@us.ibm.com \
--to=pgilliam@us.ibm.com \
--cc=gdb@sources.redhat.com \
--cc=msnyder@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