From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LitNd-0007N6-OO
	for qemu-devel@nongnu.org; Sun, 15 Mar 2009 12:40:05 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LitNZ-0007Mb-Ff
	for qemu-devel@nongnu.org; Sun, 15 Mar 2009 12:40:05 -0400
Received: from [199.232.76.173] (port=34601 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LitNZ-0007MY-DH
	for qemu-devel@nongnu.org; Sun, 15 Mar 2009 12:40:01 -0400
Received: from mx2.redhat.com ([66.187.237.31]:55289)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1LitNY-0003Fk-Qd
	for qemu-devel@nongnu.org; Sun, 15 Mar 2009 12:40:01 -0400
Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26])
	by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n2FGdxX3023479
	for <qemu-devel@nongnu.org>; Sun, 15 Mar 2009 12:39:59 -0400
Message-ID: <49BD2F5D.7030105@redhat.com>
Date: Sun, 15 Mar 2009 18:39:57 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: SIGSEGV on Windows with KQEMU enabled
References: <gosfo1$575$1@ger.gmane.org>	<gpe5da$4i1$1@ger.gmane.org>	<alpine.DEB.1.00.0903141315430.10279@pacific.mpi-cbg.de>	<200903150042.58341.paul@codesourcery.com>
	<49BD29F2.9000400@mail.berlios.de>
In-Reply-To: <49BD29F2.9000400@mail.berlios.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Stefan Weil wrote:
> This change changes the location of variable cur_mon from BSS to DATA
> segment.
> For buggy code, such changes surely can have an effect. Maybe some other
> variable in data which is located before cur_mon destroys cur_mon.
>
> Running in gdb with a hardware watchpoint on any change of cur_mon might
> help
> to see if cur_mon is overwritten.
>   

Another way to debug these issues is to look at the symbol map of a 
known bad executable, and examine uses of variables immediately before 
and after the corrupted variable.  I've recently found a bug using this 
method.

-- 
error compiling committee.c: too many arguments to function