From: Mark Wielaard <mark@klomp.org>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: frysk-core/frysk/proc ChangeLog TestBreakpoint ...
Date: Fri, 13 Oct 2006 15:57:00 -0000 [thread overview]
Message-ID: <1160754997.3025.18.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <452F99F3.60303@redhat.com>
Hi Andrew,
On Fri, 2006-10-13 at 09:51 -0400, Andrew Cagney wrote:
> Mark Wielaard wrote:
> >
> > I read that but it doesn't give an explanation for this change.
> >
> It stops the hang.
Yes, it claims that. But why did that hang happen and how does your
change help? As far as I can see there isn't a change of functionality
just a duplication of code. So please do explain the change a little
more. When we understand the cause of the problem we might be able to
fix it without needing to duplicate code.
Thanks,
Mark
next prev parent reply other threads:[~2006-10-13 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061012145206.6642.qmail@sourceware.org>
2006-10-12 20:46 ` Mark Wielaard
2006-10-12 21:20 ` Andrew Cagney
2006-10-12 23:20 ` Mark Wielaard
2006-10-13 13:51 ` Andrew Cagney
2006-10-13 15:57 ` Mark Wielaard [this message]
2006-12-11 22:01 ` 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=1160754997.3025.18.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).