From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: SIGSEGV on Windows with KQEMU enabled
Date: Sun, 15 Mar 2009 18:39:57 +0200 [thread overview]
Message-ID: <49BD2F5D.7030105@redhat.com> (raw)
In-Reply-To: <49BD29F2.9000400@mail.berlios.de>
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
next prev parent reply other threads:[~2009-03-15 16:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 0:39 [Qemu-devel] SIGSEGV on Windows with KQEMU enabled Consul
2009-03-07 2:51 ` Anthony Liguori
2009-03-13 1:28 ` [Qemu-devel] " Consul
2009-03-13 10:37 ` Johannes Schindelin
2009-03-13 17:33 ` Consul
2009-03-14 12:16 ` Johannes Schindelin
2009-03-14 12:36 ` Andreas Färber
2009-03-15 0:42 ` Paul Brook
2009-03-15 16:16 ` Stefan Weil
2009-03-15 16:39 ` Avi Kivity [this message]
2009-03-16 10:22 ` Johannes Schindelin
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=49BD2F5D.7030105@redhat.com \
--to=avi@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.