From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [patch]: Replace stryoul call to fetch address
Date: Thu, 28 Feb 2013 00:33:00 -0000 [thread overview]
Message-ID: <512E7AFE.8020909@redhat.com> (raw)
In-Reply-To: <20130227200553.GB5873@ednor.casa.cgf.cx>
On 02/27/2013 08:05 PM, Christopher Faylor wrote:
> Just to be a little less terse: The quoted email is me commenting on the
> fact that someone submitted a patch which "#if 0"ed some code. I was
> commenting on the '#if 0' not on the fact that cygwin's signal handling
> with gdb is broken. AFAIK, it is working. If it isn't working then I
> would never suggest that ripping out code was the right solution.
I was actually thinking of this:
http://www.sourceware.org/ml/cygwin-developers/2007-02/msg00052.html
and IIRC some other messages on the cygwin lists in the past I
had found at the time of that question. But it's useless to look
for them.
So you're saying that Cygwin actually does output the "cYgSiGw00f"
stuff nowadays?
--
Pedro Alves
prev parent reply other threads:[~2013-02-27 21:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 16:44 Corinna Vinschen
2013-02-27 17:20 ` Pedro Alves
2013-02-27 18:47 ` Corinna Vinschen
2013-02-27 19:40 ` Pedro Alves
2013-02-27 19:53 ` Corinna Vinschen
2013-02-27 20:03 ` [patch] gdbserver/win32-low.c: Fix printf-like formatting (was Re: [patch]: Replace stryoul call to fetch address) Corinna Vinschen
2013-02-27 21:05 ` Eli Zaretskii
2013-02-27 21:25 ` Corinna Vinschen
2013-02-27 21:30 ` Eli Zaretskii
2013-02-28 9:19 ` Corinna Vinschen
2013-02-28 16:20 ` Eli Zaretskii
2013-02-27 21:50 ` Pedro Alves
2013-02-28 11:01 ` Corinna Vinschen
2013-02-28 0:44 ` [patch]: Replace stryoul call to fetch address Pedro Alves
2013-02-28 10:02 ` Corinna Vinschen
2013-02-28 16:33 ` Corinna Vinschen
2013-02-28 16:48 ` Corinna Vinschen
2013-02-28 17:04 ` Pedro Alves
2013-02-27 20:24 ` Christopher Faylor
2013-02-27 20:29 ` Christopher Faylor
2013-02-28 0:33 ` Pedro Alves [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=512E7AFE.8020909@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@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