Re: ZClasses OO Library contributed
On Fri, 10 Dec 2004 18:02:56 -0800, Matt Lewis
<guest at RapidEuphoria.com> wrote:
>The other thing that needs to be done is to figure out how to implement
>tracing. I've been thinking about writing a tracing app using wxEuphoria.
>It will either be a dll/so, or a combination dll/so plus stand alone app
>that will talk to the dll/so via sockets or something. I'm thinking
>a standalone app, because you could have it running in the background,
>and your data could persist after the main process shuts down. Also,
>you could debug multiple processes at once in the same app (which might
>or might not be a good thing). Either way, I suspect that I'll implement
>a standard API so that others can write better debuggers than me (Pete
>Lomax, where are you? :).
I'm here 
In execute.e, opSTARTLINE() as released only has code for trace(3) and
just needs extra code for trace(1), with all the info needed for the
trace display available in slist[a]. I just tested this and trace(1)
under eu.ex creates a ctrace.out, so this routine is already called as
and when needed.
I haven't tried calling RTLookup(), nor examined find_line(),
show_var(), or trace_back() [all in execute.e], as RL is keeping me a
tad busy these days, but between them you should be able to find all
the info and tips you need for displaying variables.
The Posetf trace works via a hardware debug register and isn't
applicable to RDS IL in any shape or form I can see.
Regards,
Pete
|
Not Categorized, Please Help
|
|
