Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 428
  • Last Modified:

Difference in Win Dbg and Visual Studio Debugger

When I am attaching to a process using Visual Studio Debugger my program run's fine.  When I am attatching using the Windows Debugger(not very fimilar with this) I am catching a snag on some exception.  Why is this?  Which debugger should I really use?
0
cophi
Asked:
cophi
  • 4
  • 3
1 Solution
 
jkrCommented:
What kind of exception?
0
 
cophiAuthor Commented:
an exception on ntdll.dll.  I doubt the exception is actually thrown inside of that, but other than that it just spits out a bunch of address information...
0
 
jkrCommented:
Hm, I assume that is a 'First Chance Exception'? If so, you can simply ignore it, that only means that an SEH exception was handled successfully.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
cophiAuthor Commented:
I don't understand tho, In the Visual Studio Debugger I selected to break into the debugger on any first chance exceptions yet none are thrown.  Why is one thrown when using the Windows Debugger even if its only a first chance exeception?
0
 
jkrCommented:
That would indeed be odd. What is the exact exception information given by WinDbg?
0
 
cophiAuthor Commented:
(7d0.360): Break instruction exception - code 80000003 (first chance)
eax=7ffd7000 ebx=00000001 ecx=00000002 edx=00000003 esi=00000004 edi=00000005
eip=7c901230 esp=0571ffcc ebp=0571fff4 iopl=0         nv up ei pl zr na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00000246
ntdll!DbgBreakPoint:
7c901230 cc               int     3

Doesn't really mean much to me.... but I do not get any exceptions when running visual studio
0
 
jkrCommented:
*g* - the line

(7d0.360): Break instruction exception - code 80000003 (first chance)

pretty much tells it all - this is a hard-coded breakpoint aka

__asm { int 3; }

in the function 'DbgBreakPoint()' and it is 'first-chance'. Visual Sudio probably does not catch it since the exception 0x80000003 is not listed in the exception VS handles, at least not in the default setup (just checked it). Try to add this exception code to the list and see what happens.
0
 
itsmeandnobodyelseCommented:
>>>> Visual Sudio probably does not catch it

User breakpoint 3 is the way Visual Studio debugger handles assertions. I assume when using a different debugger you would need to change 'Debug Info' from 'Program Database' == *.pdb to C7 as there are too many specials in pdb than can't be handled by a different debugger.

Regards, Alex


0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now