Visual Studio 2008: How to view disassembled code for a DLL that is not executing at the moment

I'm using Visual studio 2008 to track down a bug in an executing process. I have attached to the process and identified the module of interest. (It happens that debug symbols for this module have been loaded from a pdb file.) I want to show the disassembled code in the Disassembly window so that I can decide where to set a breakpoint.

When I break the process, the currently executing module is shown in the Disassembly window. Un开发者_开发技巧fortunately, this is not the module of interest. I can't figure out how to show the code for the module of interest while it is not executing.

Assuming you are debugging an unmanaged process...

When you "Debug/Break All", follow these steps:

Choose "Debug/Windows/Modules" to get a listing of all loaded modules. Under the "Address" column in the Modules window is the memory range for that module. In the "Address:" box in your disassembly window, type in the start address for the module (make sure to add 0x before the number)

You should now be at the start of the module you want to play with. If you know the address of a function, you can just jump to that address.

Here's an example:

Run sol.exe Attach to the process, and break all. Look at the modules, and find "cards.dll", you'll see it loads at 6fc10000 (on my machine, anyway).

Type that address (0x6fc10000) into the disassembly window, and it will bring you to the start of the module.

Now say I want to actually jump to a function. Open the DLL in Dependency Walker (depends.exe) to get the offsets of the functions. In my example, I want to set a breakpoint on the function "cdInit". In Dependecny Walker, it shows that the offset to the exported function cdInit is 0x000013e6. So to get to that function, I would add the start address of the module (0x6fc10000) to the offset (0x000013e6) to get 0x6fc113e6.

Typing this address into the disassembly box does indeed jump me right to the start of that function.

Doing stuff like this is far easier in WinDbg

uf cards!cdInit

Have you tried using the .Net Reflector? You could get all of the code from your DLL and possibly even recompile it with debugging messages in it. It's free:

http://www.red-gate.com/products/reflector/

Cheers