Re: [Qemu-devel] Re: SIGSEGV on Windows with KQEMU enabled

[Avi Kivity]

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