Lorenzo Campedelli wrote:
> Along the same lines, when a breakpoint is set execution is correctly
> interrupted but gdb instead of reporting the breakpoint hit gives, for
> the
> same instruction:
>
> Program received signal SIGSEGV, Segmentation fault.
> kmain () at main.c:60
> 60 {
>
> I verified that the value of (context.event_info & 0xff) in mywait()
> is actually 13.
The reason for this is that int3, which is what GDB overwrites
the instruction with, corresponds to an invalid entry in the
guest IDT, which makes it GPF == 13 (anyway that's
what I think it is...)
> Note also that neither STEP nor NEXT seem to work: they behave like
> CONT.
What does typing "si" do ?
-- Ramon
