https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #30 from Jidong Xiao <jidong.xiao@xxxxxxxxx> --- 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. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
