Topaz Filer: if you use e-mail for business, we can save you money and decrease your risk.
Can not enable JIT debugging
Messages   Related Types
This message was discovered on microsoft.public.vsnet.debugging.
Responses highlighted in red are from those people who are likely to be able to contribute good, authoratitive information to this discussion. They include Microsoft employees, MVP's and others who IMHO contribute well to these kinds of discussions.

Yuan Ze
I can't enable JIT debugging for an application written in C#. This app
depends on some Mixed Mode managed C++ Libs. When exceptions generated in
it, no JIT debugger invoked. Only the default dialog box shows up. I have
enabled JIT debugging for window forms in machine.config and app.exe.config,
but it doesn't work. Even if I debug this app in IDE, the "break" button is
unavailable. But pure C# applications have no problems.

Any help would be great appreciated.

Reply to this message...
Vote that this is a GOOD answer...
 
Auto-following on Twitter
Ubuntu and XP on one “desktop”
 
    
Gregg Miskelly (VIP)
What do you mean by 'the default dialog'? Are you crashing in managed code
or native code?

If managed code, what are these registry keys set to? Also, are you crashing
on the main thread?
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgJITDebugLaunchSetting

If native code, what is this registry key set to?
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\AeDebug\Debugger

--
Gregg Miskelly
http://blogs.msdn.com/greggm

This posting is provided "AS IS", with no warranties, and confers no rights.
"Yuan Ze" <Click here to reveal e-mail address> wrote in message
news:Click here to reveal e-mail address...
[Original message clipped]

Reply to this message...
Vote that this is a GOOD answer...
 
 
    
Yuan Ze
Thank you for your help.

"the default dialog" is the dialog displays the stack trace information when
exceptions generated. I think this dialog is created by cordbg.exe. To test
my code, I managed to throw exceptions in C#. So the crashing is in managed
code.

The values under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\ are
set to
DbgJITDebugLaunchSetting 2
DbgManagedDebugger ...vs7jit.exe...
The registry key DbgManagedDebugger is set to cordbg.exe. The
AeDebug\Debugger is set to ..vs7jit.exe...

"Gregg Miskelly" <Click here to reveal e-mail address> wrote in message
news:#Click here to reveal e-mail address...
[Original message clipped]

Reply to this message...
Vote that this is a GOOD answer...
 
 
 




Ad
BootFX
Reliable and powerful .NET application framework.
Recession Busting Bespoke Software
Get through the recession by investing in bespoke software to decrease costs and create commercial opportunities.
Other DN247 Network Sites
.NET 247
SQL Server Wins
Old Skool Developer
 
Copyright © AMX Software Ltd 2008-2009. Portions copyright © Matthew Baxter-Reynolds 2001-2009. All rights reserved.
Contact Us - Terms of Use - Privacy Policy - .NET 247 is a member of the DN247 Network - 4.0.30129.1734