I'm having trouble getting OllyDbg to display my MASM symbols correctly.

At this location ("http://board.win32asmcommunity.net/attachment.php?s=&postid=71248") I have uploaded a very simple example program that demonstrates this problem (a RadASM project file is also included, where all compile/link switches can be seen).


The main procedure looks like this:


<pre>
main proc
jmp example_label
nop
nop
example_label:
invoke MessageBox, 0, ADDR mbMessageText, ADDR mbTitleText, MB_OK
jmp another_label
nop
nop
another_label:
ret
main endp


</pre>


What I want is to get the labels "example_label" and
"another_label" to be displayed in the debugger,
but it refuses to do this. Some other labels are
displayed though, e.g. the "main" symbol, and the
"mbMessageText" and "mbTitleText" symbols in the
data section. Does anyone have any idea about how
to get the debugger to display the two other labels
too?

It would be really nice if someone would take a look and explain if I'm doing something wrong (or confirm that you get the same problem in OllyDbg).

Thanks a lot!

dELTA: i look tomorrow, but in the meantime - question: why do you need for ?
below CPU disassm you have the line from the source file where it shows "jmp another_label". if you want more you can export map file and then import using mapconv plugin (not so nice though)

The problem with the single source line below the disasm window is that I don't think it gives any good overview at all. It is very inefficient and inconvenient to have to take my eyes off the disasm window after every single instruction step when tracing the program, just to see if the source line has changed, and what it is (most often only to see the exact same instruction that is listed in the disasm).

I have tried to bring up the source window in parallel with the disasm window when single stepping, and this is quite ok, except for the very annoying fact that it does not scroll automatically when the execution point jumps outside of the current viewed area. This makes me having to scroll manually in the source all the time, which in equally inconvenient and impractical as the single source line, if not worse. I have already mailed Oleh about making the source window scroll to follow the execution point automatically, so I'm really hoping for the best with that one.

Anyway, having the labels inside the actual code can be better and more efficient than viewing the source code in many situations too, so I'd really like to get all the memory adresses show their labels in this one too, and not just some of them.

Anyway, very nice of you to take a look at it TBD, I'm looking forward to hear about what you find!

Thanks!

dELTA: i cannot find a way to include the labels in the disasm window. i think is how the OllyDbg uses the pdb info because the info is inside.

did you stress Olly in the mail with this problem, or should i send him too ?

I haven't mailed him about this yet, so you are very welcome to do so. You know him better too, so hopefully it will have a better effect if you mail him. Anyway, it should not be very hard for him to fix this I think, because the functionality to mark memory positions with labels is already fully in the program (it can be done manually), it just seems like he doesn't extract the labels from the pdb data right now, just as you say.

Thanks!