WinDbg Problem

[shankle]

I have my source code up on the screen.
I scroll down to where I want to put a breakpoint and hit F9.
The line turns red. I hit F5. Nothing happens. The red line
does not turn blue and Step Over goes nowhere????????????

Thanks for any guidance,
JPS

[trodon]

ilegal step  :bg

[sinsi]

umm...because go (F5) doesn't get to the breakpoint?

[shankle]

The spot I was in the program should have been able to get to with F5.

I know Hutch likes messageboxes for debugging but my problem could have been
solved in 5 minutes with a good SYMBOLIC debugger. The messsagebox routine took
2 days. I needed to look at memory and my problem would have been solved. Kind of
diffiucult with messageboxes.

I'm going to look again at Jeremy Gordons GOBUG. The compiling and linking with MASM32
gets tricky. I'm sure it's covered somewhere on this forum. 

[sinsi]

...I needed to look at memory...

What about View->Memory?

[PBrennick]

After you set the breakpoint, did you start the program?  If you did not, of course nothing is going to happen.

Paul

[Vortex]

shankle,

Have a  look at Ollydbg, it's a very powerfull tool :

http://www.ollydbg.de/

[shankle]

I set the breakpoint and hit f5. I thought that started it and ran to the breakpoint.

I don't use Ollydegug because I want to look at the source code (with Symbols)
only and not the disassembled code.

Jeremy Gordon's GOBUG  is kind of like what I mean but I get the impression that I would
have to code in GoAssembly and Golink. To many changes to switch Assemblers.

I'm was weaned on a product called CodeView, which did what I needed.
But alas it's no more.

Sorry to take up time and space with this.

[BogdanOntanu]

Ollydbg is a symbolic debugger also...
Aparently It is just the fact that you do not want to put some honest efforts into researching this ;)

I am always amazed to notice how begginers (or people asking questions) always ignore answers because they "know better" :D

[jorgon]

Shankle

Jeremy Gordon's GOBUG  is kind of like what I mean but I get the impression that I would
have to code in GoAssembly and Golink. To many changes to switch Assemblers.

No you don't need to use GoAsm and GoLink to get GoBug to show symbols in its disassembly.
Just ensure that your program is compiled with symbols either embedded in the exe, or in a separate dbg or pdb file.
How you do this depends on which assembler/compiler and linker you are using.  You just have to specify the correct switch.
There is some help from the GoBug help file about this.
GoBug shows its disassembly in assembler, but you can view your source in a separate window.  This allows you to compare the source with the disassembly.

[shankle]

Thanks Jorgon. Will research GOBUG  some more but I think that's what I am looking for.
JPS