trace v1.00

[Guy]

Hi Xbliters,

I just uploaded trace_v1_00.zip in the Google file area.
It contains:
- trace_gen.vxn (the VIXEN project)
- trace.x (the xblite source)
- trace.rc (the ressource file)
- trace.manifest (the XP style)
- 3 icons:
. FileList.ico
. KO.ico
. OK.ico
- trace.ini (the reopen file list)

trace.x is using solely Callum Lowcay's WinX library; that's why I did
not bother creating an application's icon since WinX's icon is used
intead as the default icon.

trace.exe is merely a toy as I mainly wanted to acquire a better
command in WinX's coding. However, I used it with success for
debugging functions in VIXEN.

I think that this tool could be improve by writing the trace in a log
file. I will code this evolution if requested in this Group by some
interested Users. In the mean time, study the source and give me a
feedback; use trace and share your comments on its usability.

Bye! Guy

[Guy]

Hi Xbliters,

Well, I convinced myself that trave.x would remain a toy if it did not
trace a program in its log file. So enters trace v1.01!-)

I uploaded trace_v1_01.zip in the Group's file area, at
http://xblite.googlegroups.com/web/trace_v1_01.zip

And remember, I welcome all feedback from my fellow Xbliters :)

Enjoy! Guy

[Guy1954]

Hi Xbliters,

I am very interested to know if you find useful the "KISS trace
facility" that I posted in the Group's file download area. I know that
it saved me hours in debugging VIXEN but all that I know is my own
experience.

Bye! Guy

[bushpilot]

Hi Guy,

I tried looking at it, but honestly didn't understand how to use it.
It does sound interesting.

Greg

[Guy1954]

Hi Greg,

trace.exe asks for an xblite program source and creates a new source
with all executable statements followed by a write of it in a log file
(x.log by default).

The size of the resulting source is about the double because of that
"echo" to the log.

Imagine you want to trace a piece of code (say 20 lines of code).
You open the original source in XSed and the processed program in a
text editor. You locate the piece of code you want to trace, look for
the processed source and extract the exact same piece of code (should
be 40 lines of code) and replace the original piece of code.

Compile/link/run. Open x.log in an editor and watch the trace in the
log.

Guy

[lzdude69]

Hi,

I think this is a cool idea, but what is the advantage of doing this
to just sticking a ? "asdad" after/before whatever line you are
investigating? Possibly a stupid question I guess:P

[Guy1954]

Hi Rhett,

The idea is to have all the xblite statements written in a log file
right after they have been executed. If the program crashes, the
"crashing" statement won't be in the log file but the previous one
will.

Actually, it might be a good idea if trace.exe would write the
statement BEFORE it is actually executed as the faulty statement will
be the last written in the log file. What say you?

Bye! Guy

[Guy1954]

I just uploaded trace version 1.03, which writes the traced statement
in the log file BEFORE it is actually executed. Enjoy! Guy