I've long had a book called "Debugging Applications" and it's been a good book (not to be confused with Debugging Windows Applications which I also have)... the CD has a complete e-book of itself and, there is sourcecode to a debugger called WinDBG which is a fully functional Windows GUI Debugger with breakpoint support, and disassembly, register viewing and so on...

If anyone wants to write a debugger for RadASM or something, that would be a good place to start. The code is well written.



Thanks,
_Shawn
Posted on 2002-08-25 12:23:21 by _Shawn
Hi Shawn,

I'm a little confused about this debugging thing.

I've probably written hundreds of programs and
some with very nasty bugs and all I use is my
little debug program that has an option of
displaying a reg or dw value on the Titlebar,
Statusbar or in a message box. The message box
display will halt the program. It also has an
option of displaying all of the regs in a message
box.

If I want to display three values I put one on
the Titlebar, one on the Stausbat, and one in a
message box and when the program halts I have
three values to look at.

Or I can use several message box displays through
out the program used as break points to isolate
where the program crashes.

BTW. My little debug program is a modified version
of Hutchs's debug program.

I also use a message box to display text.

I've tried Softice a couple of times, but by the
time I got everything setup and looked at the
output I could have fixed the bug ten times over
with my method.

Just my 2 cents worth.

Ewayne
Posted on 2002-08-25 19:00:35 by Ewayne
Hi Ewayne,

so you're basically saying that a message box is enough is enough. I think that's just a habit of yours. I agree vkim's debug macros are great, but sometimes you want more. Moreover, when it takes only a single keyboard shotcut to fire up Olly from Radasm. Also a sophisticated debugger is great for learning, e.g. to see how flags are affected by different instructions in real time, etc.
Posted on 2002-08-25 19:44:01 by ramzez
To ramzez:

As long as the message box displays the information
that I feed it from my debug program yes.

My little program can also display the flags.

It can also be done with one key stroke from
AsmEdit.

It's not a habit, it's a way of life.

Ewayne
Posted on 2002-08-25 20:13:35 by Ewayne
I'm writing a little debugger for MASM32 package. I think it will allow to do the following:
1. Trace source code step by step.
2. Watch variables (local and global), registers and flags.
3. Set breakpoints with conditions.
I do only first steps and if someone wants to help me then write to me. :)
Posted on 2002-08-26 00:07:51 by vkim
Hi all

I fully agree with Ewayne here. A debugger just gives too much info and hence is slow to use. I only use Ollydbg as a JIT debugger, and as such it is excelent. I mostly use vkim's macros, and once in a while just a msgbox.
Analysing my needs this is what I really want:

1. Select a block of code that I want to single step with a popup showing register values.
2. A marker must show in the IDE the line about to be executed.
3. It must be possible to turn off debugging the block at runtime at will.
4. It must be possible to debug without having to add includes or macros to the source.
5. It must be easy to add and remove blocks from debugging.

I dont think this is very difficult to do. I just need a macro that calls a function in a dll, with line number and module as parameters. The dll would handle adding and removal of the macro and macro calls and also the debug indicators in the IDE.

KetilO
Posted on 2002-08-26 02:31:21 by KetilO