From: Stan Shebs <stan@codesourcery.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [OB] Fix syntax error in record_resume
Date: Tue, 01 Sep 2009 19:17:00 -0000 [thread overview]
Message-ID: <4A9D7354.5010207@codesourcery.com> (raw)
In-Reply-To: <daef60380909010454k411d62f2pea6f911b5664778d@mail.gmail.com>
Hui Zhu wrote:
> * record.c (record_resume): Change "siggnal" to "signal".
>
FYI, a number of places in the code use "siggnal" for the variable name,
or some other name that is not "signal". Once upon a time some hosts
did nasty macro tricks with "signal" in their system headers, so it was
better for portability to use some other string. I don't know if this
is still an issue though.
Stan
next prev parent reply other threads:[~2009-09-01 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 11:54 Hui Zhu
2009-09-01 19:17 ` Stan Shebs [this message]
2009-09-01 19:21 ` Michael Snyder
2009-09-02 1:28 ` Hui Zhu
2009-09-02 1:33 ` Hui Zhu
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=4A9D7354.5010207@codesourcery.com \
--to=stan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=teawater@gmail.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