Re: [Qemu-devel] Add native debugger

2011-11-28 Thread felix.matenaar@rwth-aachen
Hi, gen_intermediate_code_internal in ./target-i386/translate.c is a good starting point. This is where Basic Blocks are translated into native code by TCG. I recently did some patches for program analysis in the i386 part so dont hesitate to contact me. regards, felix

Re: [Qemu-devel] Add native debugger

2011-11-27 Thread Rick Hodgin
Andreas, Thank you. I guess I'll go back to Bochs. Things are simpler there. :-) I do appreciate your help. Thanks and best regards, Rick C. Hodgin --- On Sun, 11/27/11, Andreas Färber wrote: > From: Andreas Färber > Subject: Re: [Qemu-devel] Add native debugger > To: "

Re: [Qemu-devel] Add native debugger

2011-11-27 Thread Andreas Färber
Am 27.11.2011 15:12, schrieb Rick Hodgin: > --- On Sun, 11/27/11, Blue Swirl wrote: >> On Sun, Nov 27, 2011 at 04:10, Rick >> Hodgin >> wrote: >>> For i386, I'm considering writing a native debugger >> for QEMU that is not GDB. It would allow a separate/new >> windowed interface which would show

Re: [Qemu-devel] Add native debugger

2011-11-27 Thread Rick Hodgin
Blue, --- On Sun, 11/27/11, Blue Swirl wrote: > On Sun, Nov 27, 2011 at 04:10, Rick > Hodgin > wrote: > > For i386, I'm considering writing a native debugger > for QEMU that is not GDB. It would allow a separate/new > windowed interface which would show disassembly, registers, > stack, local v

Re: [Qemu-devel] Add native debugger

2011-11-27 Thread Blue Swirl
On Sun, Nov 27, 2011 at 04:10, Rick Hodgin wrote: > For i386, I'm considering writing a native debugger for QEMU that is not GDB. > It would allow a separate/new windowed interface which would show > disassembly, registers, stack, local variables, memory windows, etc., > allowing the user to si

[Qemu-devel] Add native debugger

2011-11-26 Thread Rick Hodgin
For i386, I'm considering writing a native debugger for QEMU that is not GDB. It would allow a separate/new windowed interface which would show disassembly, registers, stack, local variables, memory windows, etc., allowing the user to single-step through code and trap opcodes like INT 1, INT 3,