public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jerone Young <jyoung5@us.ibm.com>
To: kvm <kvm@vger.kernel.org>
Subject: [kvm-userspace] new functions on_vcpu() causing segafault when trying to use breakpoints
Date: Fri, 30 May 2008 14:27:48 -0500	[thread overview]
Message-ID: <1212175668.24409.9.camel@thinkpadL> (raw)

New code recently added to the repository has made some modifications to
the kvm_update_debugger() function in qemu-kvm.c. Where as no longer  to
just call kvm_guest_debug...Now there is a new fuction on_vcpu() that
places things in work queues and launches them.

The problem is when kvm_invold_guest_debug() gets called, it segfaults
calling kvm_guest_debug().

What exactly is the point of complicating this? 

This code does segfault on x86 also. For now I have just placed the old
code back locally.

 


             reply	other threads:[~2008-05-30 19:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30 19:27 Jerone Young [this message]
2008-05-30 20:23 ` [kvm-userspace] new functions on_vcpu() causing segafault when trying to use breakpoints Jan Kiszka
2008-05-30 20:55   ` Jerone Young

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=1212175668.24409.9.camel@thinkpadL \
    --to=jyoung5@us.ibm.com \
    --cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox