Damien O'Brien wrote:
>> I tested this by setting a breakpoint at the start of DllMain in my
component and attaching to Mozilla in the VS.Net debugger. My
breakpoint
was never hit, indicating that my dll was not being loaded.
I then took a look at mozilla using process explorer as you did. With
process explorer it seemed to indicate that my dll was being accessed
in
some way as my DLL was appearing in the list of DLLs. But the fact that
DllMain wasn't being hit when debugging indicated that it wasn't
actually being loaded.
<<
I don't know about VS.NET, but in older versions of DevStudio (6 on my
PC) if you attach to a process for debugging - you cannot set a
breakpoint on a module that has not been loaded yet.
Now you can FORCE a breakpoint anywhere in your code by adding an "_asm
{int 3}". It's definitely something you don't want to leave in your
production code ;-)
_______________________________________________
Mozilla-xpcom mailing list
[email protected]
http://mail.mozilla.org/listinfo/mozilla-xpcom
