Re: [Rcxemul-discussion] Debugger

[Andy G. <gom...@ea...>]

Doh!  I keep hitting reply and sending all the messages straight to David.
Here is my reply:

Debugging in a mixed code environment is going to be hard, since you can't
use the JDI and related technologies on C code.  Just attach a debugger (gdb
most likely) to the process.  Doing a Java version would require lots of
communications code, reporting about the next instruction to be executed by
the virtual processor, and then the Java app sending a respose whether or
not to execute that instruction.

----- Original Message -----
From: "David Edwards" <d.a...@nt...>
To: <rcx...@li...>
Sent: Thursday, October 17, 2002 9:49 AM
Subject: [Rcxemul-discussion] Debugger


> Hi.
>
> Is anyone interested in helping create a debugger (in Java) to accompany
my emulator? I'm getting to the point where I need to break into certain
functions to see what's happening (specifically to try to work out why no
response is being generated when unlock firmware is called).
>
> I plan on making "debug" a compilation option of the emulator to avoid
unnecessary overhead.
>
> Any takers?
>
> Dave.
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: viaVerio will pay you up to
> $1,000 for every account that you consolidate with us.
> http://ad.doubleclick.net/clk;4749864;7604308;v?
> http://www.viaverio.com/consolidator/osdn.cfm
> _______________________________________________
> Rcxemul-discussion mailing list
> Rcx...@li...
> https://lists.sourceforge.net/lists/listinfo/rcxemul-discussion