Re: Remote debugging a mixed DLL
- From: "Olivier Matrot" <olivier.matrot.rte@xxxxxxxxxxxxx>
- Date: Thu, 21 Dec 2006 16:11:21 +0100
Hi Jeffrey,
This is a typo in the first post. The problem was about the managed part of
the symbols loading. Because in native code symbols are embedded in the DLL,
I did not paid attention to the PDB file that is produced with a mixed
assembly.
Anyway, thanks for your feedback, It's always a pleasure to submit questions
in the newsgroups.
Best regards,
Olivier.
""Jeffrey Tan[MSFT]"" <jetan@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:HePB2nxIHHA.2488@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi Olivier,
Glad to see you resolved the problem yourself. It seems that it is really
the symbol loading problem.
A little question: in your first post, you posted the following problem:
I'm still unable to set breakpoint in Native code.
But, in your second reply, you stated:
Now breakpoints in managed code are working fine
So, can you confirm if your problem is the managed or native breakpoint
not
working? Do you still need any help over this issue? Thanks.
Yes, VS2005 debugger provides much better support over symbol loading. In
"Modules" window, once you find one module's symbol is not loaded, you may
right click this row and choose "Symbol Loading Information..." menu item.
The popup dialog will reveal all the symbol probing paths for this module.
Then you may add another symbol path or copying the assembly symbol file
to
the one of the existing probing path.
If you need further help, please feel free to post, thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
.
- Follow-Ups:
- Re: Remote debugging a mixed DLL
- From: "Jeffrey Tan[MSFT]"
- Re: Remote debugging a mixed DLL
- References:
- Remote debugging a mixed DLL
- From: Olivier Matrot
- Re: Remote debugging a mixed DLL
- From: Olivier Matrot
- Re: Remote debugging a mixed DLL
- From: "Jeffrey Tan[MSFT]"
- Remote debugging a mixed DLL
- Prev by Date: RE: how to debug com interop in vs2005 under Vista
- Next by Date: Re: Remote debugging a mixed DLL
- Previous by thread: Re: Remote debugging a mixed DLL
- Next by thread: Re: Remote debugging a mixed DLL
- Index(es):
Relevant Pages
|