From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: pedro@codesourcery.com (Pedro Alves)
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: [4/7] Adjust the ttrace target (HP-UX) to always register the
Date: Sun, 10 Aug 2008 21:16:00 -0000 [thread overview]
Message-ID: <20080810211545.7634D4EBE@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <200808102205.08109.pedro@codesourcery.com> from "Pedro Alves" at Aug 10, 2008 10:05:07 pm
> > I've just tried Pedro's second and third patches for 4/7.
>
> Now *I've* lost track here. I thought that the "ttrace: Protocal
> error" / vla6.f90 bug we were resolving was independant of my 4/7 patch
> already registering a main thread (from this thread).
Yes, I believe it is. The protocol error appeared in testing your 4/7.
As such, the majority of my testing is with all three patches applied.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
next prev parent reply other threads:[~2008-08-10 21:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 1:36 [4/7] Adjust the ttrace target (HP-UX) to always register the main thread Pedro Alves
2008-08-08 16:41 ` John David Anglin
2008-08-08 17:24 ` Pedro Alves
2008-08-08 17:49 ` John David Anglin
2008-08-08 18:34 ` ttrace: Protocal error John David Anglin
2008-08-08 20:02 ` Pedro Alves
2008-08-08 20:49 ` John David Anglin
2008-08-10 0:15 ` [4/7] Adjust the ttrace target (HP-UX) to always register the main thread Daniel Jacobowitz
2008-08-10 0:36 ` [4/7] Adjust the ttrace target (HP-UX) to always register the John David Anglin
2008-08-10 21:05 ` Pedro Alves
2008-08-10 21:16 ` John David Anglin [this message]
2008-08-10 21:04 ` John David Anglin
2008-08-14 17:55 ` Daniel Jacobowitz
[not found] <no.id>
2008-08-10 0:46 ` John David Anglin
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=20080810211545.7634D4EBE@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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