Dll debug information 1

[Diancecht]

Hi all.

I'm trying to debug and application that has several dll and ocx files generated by me. I've created debug configurations for all of them and included in the correct path.

When I try to debug the application, by attaching the process to the debugger, an access violation error is thrown (that's what I'm trying to debug). The stack shows, appart from mshtml.dll, kernel.dll and so on, one of my dlls.

However, when I select it on the stack, I just can see the decompilated code. I've checked the path on the debugger and the dll with debug configuratin is being loaded.

I also see a console message: "Cannot load symbolic information of myLibrary".

Since I cannot even see the point where the error is being produced, I'm a little stuck. Maybe anyone could give me some hints:

1.- Why the dll code is not shown?
2.- Could be possible that, even being in the stack, the actual error is not producing there?

Thank you in advance.

Cheers,
Dian

 

[xwb]

Click on Debug/Exceptions
In the dialog box that pops up, click on Stop Always.
Then run and it should break when it throws the exception: not when it catches.

 

[Diancecht]

Hi xwb, thanks for the reply.

I've also done that, but I get the same results: just assembler code, but not the actual C++ code, so it's almost useless, I've forgotten a great part of my assembler knowledge

Cheers,
Dian

 

[xwb]

Are the .pdbs in the same directory? You need the .pdb files for the debug symbols.

 

[Diancecht]

Humm, wait a minute.

I build my dll file with debug configuration and place it in the directory por library extensions.

Is that not enought to debug it? The rest of the generated files must be also present? If so, which ones and where?

Cheers,
Dian

 

[xwb]

You should be able to debug with just the .exe, .dll and .pdb files. The .pdb will tell the debugger where to pick up the source files from.

I don't know about the .ocx files. I last used them in 1994 with VB and I can't remember how they are debugged.

 

[Diancecht]

Thank you, xwb. I thought the debug information was contained in the dll. Editing the dll I saw a full path reference to the pdb file, sounds like a little strange.

Now the debugger tells me that the symbolic information is shown, that's a good beginning. Now, I'll have to find an error situation produced in my code and not in the kernel libraries.

Btw, an ocx runs and debugs the same way as a regular dll.

Thanks again.

Cheers,
Dian