OllyDbg doesn't find source code for a BCB6 p

[casterle]

While debugging a BCB6 program, I wanted to look at my source code in context. View/Source Files shows a list containing all of my modules but the Source and Source Path columns are empty (the Source path displays (Absent)).

Scanning all of the object files in my project, then running Analyze does not solve the problem.

[blabberer]

you need to compile and link with debug info and put the .pdb files in the folder
find your linker and compile switches accordingly for masm i give the post below

http://ollydbg.win32asmcommunity.net/index.php?action=vthread&forum=1& topic=40 (http://ollydbg.win32asmcommunity.net/index.php?action=vthread&forum=1&topic=40)

[casterle]

Thanks for the quick answer, but no luck. In the thread you reference, someone said that they were having success with both Delphi and BCB, but given the age of the thread that must have been with a previous version of Ollydbg.

I'm already building with full debug information, and the .tds file (what Borland produces instead of .pdb) and .map files are located in my project directory. The Borland debugger is finding the source code without problems.

Perhaps version 1.10 doesn't work with Borland debug info?

[blabberer]

sorry i dont use bcb but with masm i can fairly well use view source
in all the versions of ollydbg

so i googled a little for some info on subject matter

and here is a link from borland
http://cc.borland.com/codecentral/ccweb.exe/listing?id=15344
it tlaks about some blah to dbg try palying with it

hope it helps you a little

[casterle]

Thanks for looking into this for me.

I've already got the program you found at Borland Code Central, but unfortunately it produces an older version of the dbg file which is not compaible with current debuggers. Such is life!

I've run into another problem with OllyDbg that is much more serious and precludes me from using it on my current project - I'll start another thread on it after I find time to document the issue.

[casterle]

Follow up: The problem I was refering to above is not in OllyDbg. I am seeing the same behavior in WinDbg and the Borland debugger.