From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 65561] KVM:Entry failed on Single stepping sti instruction
Date: Sun, 25 May 2014 03:03:48 +0000 [thread overview]
Message-ID: <bug-65561-28872-K0uruq5MTj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-65561-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=65561
--- Comment #30 from Jidong Xiao <jidong.xiao@gmail.com> ---
Jatin,
I have the following program and I did test the single step for sti command,
(gdb) disas main
Dump of assembler code for function main:
0x08048414 <+0>: push %ebp
0x08048415 <+1>: mov %esp,%ebp
0x08048417 <+3>: and $0xfffffff0,%esp
0x0804841a <+6>: sub $0x10,%esp
=> 0x0804841d <+9>: sti
0x0804841e <+10>: movl $0x8048500,(%esp)
0x08048425 <+17>: call 0x8048350 <puts@plt>
0x0804842a <+22>: leave
0x0804842b <+23>: ret
End of assembler dump.
(gdb) nexti
Program received signal SIGSEGV, Segmentation fault.
0x0804841d in main ()
(gdb)
And what I have got is a segmentation fault. Since you said you triggered the
bug via a kernel module, how did you do the single step test for a kernel
module?
In the meanwhile I am studying kvm-unit-test, since Paolo said it provides a
single step test platform.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-05-25 3:03 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 17:27 [Bug 65561] New: KVM:Entry failed on Single stepping sti instruction bugzilla-daemon
2014-05-20 5:12 ` [Bug 65561] " bugzilla-daemon
2014-05-20 7:10 ` bugzilla-daemon
2014-05-20 11:03 ` bugzilla-daemon
2014-05-20 21:00 ` bugzilla-daemon
2014-05-21 4:43 ` bugzilla-daemon
2014-05-21 4:45 ` bugzilla-daemon
2014-05-21 7:13 ` bugzilla-daemon
2014-05-21 15:13 ` bugzilla-daemon
2014-05-21 15:20 ` bugzilla-daemon
2014-05-21 16:05 ` bugzilla-daemon
2014-05-21 16:30 ` bugzilla-daemon
2014-05-21 16:39 ` bugzilla-daemon
2014-05-21 16:50 ` bugzilla-daemon
2014-05-21 17:14 ` bugzilla-daemon
2014-05-21 20:30 ` bugzilla-daemon
2014-05-21 21:08 ` bugzilla-daemon
2014-05-22 2:02 ` bugzilla-daemon
2014-05-24 4:59 ` bugzilla-daemon
2014-05-24 5:27 ` bugzilla-daemon
2014-05-24 5:38 ` bugzilla-daemon
2014-05-24 5:43 ` bugzilla-daemon
2014-05-24 5:46 ` bugzilla-daemon
2014-05-24 5:51 ` bugzilla-daemon
2014-05-24 5:56 ` bugzilla-daemon
2014-05-24 6:15 ` bugzilla-daemon
2014-05-24 6:29 ` bugzilla-daemon
2014-05-24 7:24 ` bugzilla-daemon
2014-05-24 12:26 ` bugzilla-daemon
2014-05-24 23:12 ` bugzilla-daemon
2014-05-25 3:03 ` bugzilla-daemon [this message]
2014-05-25 6:46 ` bugzilla-daemon
2014-05-25 7:48 ` bugzilla-daemon
2014-05-25 7:58 ` bugzilla-daemon
2014-05-25 8:00 ` bugzilla-daemon
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=bug-65561-28872-K0uruq5MTj@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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 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.