RE: Assembly reported as built without debug info - that is not true



Hi Juan,

Thank you posting!

-----------
The following module was built either with optimizations
enabled or without debug information:..."
-----------

What could be happening? What can I do to remotely
debug this assembly?

From the error message, it seems the target assembly has been optimized or
the debugger cannot find its debug information (.pdb file) while debugging.

In order to isolate this problem, would you please provide more detailed
info about the scenario? When do you get that error message? Can you
successfully remote debug any other assembly which is not in the GAC?

I suggest you can watch the 'Modules' window (Debug | Windows | Modules)
while performing the remote debugging. You can find that specific assembly
in the Modules window's loading assemblies' list, check its 'Optimized' and
'Symbol Status' properties.

If the 'Symbol Status' field shows "Cannot find", then it should be caused
by the debugger cannot find that assembly's .pdb file. I suggest you can
copy its .pdb file to the remote machine's ..\WINDOWS\Symbols\dll\
directory.

These tests will help us get closer to resolving your issue, so I
appreciate your time in performing them. Let me know the results at your
earliest convenience. If you have any questions or concerns, please let me
know. I am standing by to help you.

Thanks!

Best regards,

Gary Chang
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.

.



Relevant Pages

  • RE: attach to process not started in debug mode?
    ... I assume your "debug mode" means the application ... assembly code for review.(A extreme example is .Net Framework assemblies, ... Microsoft Online Community Support ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.dotnet.framework)
  • RE: attach to process of .net app not started in debugger?
    ... I assume your "debug mode" means the application ... assembly code for review.(A extreme example is .Net Framework assemblies, ... Microsoft Online Community Support ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.dotnet.languages.csharp)
  • RE: Assembly reported as built without debug info - that is not tr
    ... enabled or without debug information:..." ... the debugger cannot find its debug information while debugging. ... in the Modules window's loading assemblies' list, ... Microsoft Online Community Support ...
    (microsoft.public.dotnet.framework)
  • Return argument has an invalid type - does remoting work reliably at all?
    ... > remote object, ... > remote object returns (I can debug to that point. ... "Advanced .Net Remoting" by Ingo Rammer, his website, msdn, articles on ... .Net Remoting is really a pain to work with. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Separate AppDomain
    ... This is actually because my Remote Object assembly has not been compiled ... Loading remote AppDomain & its assemblies is ok when dll files are local ... > which the callback method is defined, I took a slightly different approach. ... > AbstractCaller: MarshallByRefObj ...
    (microsoft.public.dotnet.framework.remoting)