From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-66436-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 12032 invoked by alias); 1 Sep 2009 19:21:14 -0000
Received: (qmail 12023 invoked by uid 22791); 1 Sep 2009 19:21:14 -0000
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 01 Sep 2009 19:21:06 +0000
Received: from mailhost2.vmware.com (mailhost2.vmware.com [10.16.67.167]) 	by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 9AF05130B9; 	Tue,  1 Sep 2009 12:21:05 -0700 (PDT)
Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) 	by mailhost2.vmware.com (Postfix) with ESMTP id 6392E8E7D7; 	Tue,  1 Sep 2009 12:21:05 -0700 (PDT)
Message-ID: <4A9D7413.5020707@vmware.com>
Date: Tue, 01 Sep 2009 19:21:00 -0000
From: Michael Snyder <msnyder@vmware.com>
User-Agent: Thunderbird 1.5.0.12 (X11/20080411)
MIME-Version: 1.0
To: Stan Shebs <stan@codesourcery.com>
CC: Hui Zhu <teawater@gmail.com>,   gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [OB] Fix syntax error in record_resume
References: <daef60380909010454k411d62f2pea6f911b5664778d@mail.gmail.com> <4A9D7354.5010207@codesourcery.com>
In-Reply-To: <4A9D7354.5010207@codesourcery.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2009-09/txt/msg00031.txt.bz2

Stan Shebs wrote:
> 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.

I always thought that the name "siggnal" started with a global
variable in gdb, and then just propagated (the way it's trying
to do now).   ;-)