Re: [Qemu-devel] Problems with MIPS full system emulation and breakpoints

2007-09-11 Thread Thiemo Seufer
Daniel Jacobowitz wrote: > On Fri, Apr 20, 2007 at 02:22:09PM -0400, Daniel Jacobowitz wrote: > > I have an idea. When I was talking to Paul about breakpoints > > recently, I noticed something very strange in the ARM port: it > > continues to disassemble the instruction under a breakpoint after >

Re: [Qemu-devel] Problems with MIPS full system emulation and breakpoints

2007-09-10 Thread Daniel Jacobowitz
On Fri, Apr 20, 2007 at 02:22:09PM -0400, Daniel Jacobowitz wrote: > I have an idea. When I was talking to Paul about breakpoints > recently, I noticed something very strange in the ARM port: it > continues to disassemble the instruction under a breakpoint after > generating the debug op. This is

Re: [Qemu-devel] Problems with MIPS full system emulation and breakpoints: also for FPU emulation

2007-05-03 Thread Stefan Weil
A similar patch for EXCP_AdEL seems to fix the problems with Linux floating point emulation. Linux uses self modifying code on the stack in the FPU emulation and terminates this code using "lwzero,1(zero)" (which raises EXCP_AdEL). Sometimes, a system call which follows and is also on the sta

Re: [Qemu-devel] Problems with MIPS full system emulation and breakpoints

2007-04-20 Thread Daniel Jacobowitz
On Fri, Apr 20, 2007 at 01:03:07PM -0500, Jason Wessel wrote: > At this point the program is trashed on the second time through the loop > because the translated block with the breakpoint op code was executed instead > of being flushed and translated with the correct original > instruction. I ha

[Qemu-devel] Problems with MIPS full system emulation and breakpoints

2007-04-20 Thread Jason Wessel
It seems there is an issue with the translation block flushing when writing to the code regions in the MIPS full system emulation. Using a 2.6 kernel which is basically running in single user mode, I use an extremely simple program: main () { int i; for (i = 0; i < 10; i++) { p