Hello all,
OllyDbg is a great debugger, but.. is there any way to show symbols instead of
addresses in OllyDbg, for VC2005-compiled programs (link time code generation
preferably)? I'm tired to take a look at the MAP file every second. :P
I use VC2005 only minimally, i.e. command line and without standard libraries,
all of my VC2005 is few MB's big and fits nicely, together will all my sources
and stuff, into an USB pen. So please do not ask me to use the VC2005 debugger,
my USB Pen is not 20GB big and I cannot install stuff anyway into others' PC.
Running cl.exe and OllyDbg.exe without installation is so much nicer.. :)

About the symbols, can OllyDbg show them or is it limited to OS symbols only
(which, I admit, mine doesn't show either. How do I it?).

Thanks!
Mario

spamtrap@crayne.org wrote:
>
>OllyDbg is a great debugger, but.. is there any way to show symbols instead of
>addresses in OllyDbg, for VC2005-compiled programs (link time code generation
>preferably)? I'm tired to take a look at the MAP file every second. :P
>I use VC2005 only minimally, i.e. command line and without standard libraries,
>all of my VC2005 is few MB's big and fits nicely, together will all my sources
>and stuff, into an USB pen. So please do not ask me to use the VC2005 debugger,
>my USB Pen is not 20GB big and I cannot install stuff anyway into others' PC.
>Running cl.exe and OllyDbg.exe without installation is so much nicer.. :)
>
>About the symbols, can OllyDbg show them or is it limited to OS symbols only
>(which, I admit, mine doesn't show either. How do I it?).

I, also, am hoping there is a way to do this.  Last I knew, OllyDbg was
written in Delphi and didn't understand the Microsoft-format symbols.
-- 
- Tim Roberts, timr@probo.com
  Providenza & Boekelheide, Inc.

You must have symbols in your EXE file.
Add "/DEBUGTYPE:COFF" at link time.

Best regards.

Mario wrote:

> About the symbols, can OllyDbg show them or is it limited to OS
symbols only
> (which, I admit, mine doesn't show either. How do I it?).

I dont't know how for VC2005, but for Assembler (MASM) I always use:
ml /c /coff /Cp /Zi   ; (Zi = add symbolic debug info)(to .obj)

link /subsystem:windows /debug   ; (debug  = Creates debugging
information)

This will create a big .PDB -file (program database) along with the
...exe

I think OllyDbg is getting then informations from this.PDB by the use
of DbgHelp.dll (MS debug help library).

Then the window in the middle of OllyDbg will look like this:
0040A97A=SDB.get_esi_line_len
sdb.asm:1402.  call    get_esi_line_len

(SDB = modulename, get_esi_line_len = Procedure name, sdb.asm = source
file, 1402 = source line number, "call  get_esi_line_len" = source line
text)


[-> MSDN (Library): Linker Reference, dbghelp.dll, .PDB files]

hope it works.