Re: Breakpoints firing inside mscorwks.dll
From: Tarek Madkour [MSFT] (tarekm_at_online.microsoft.com)
Date: 02/23/05
- Next message: David Liebtag: "Debugging DLL built from command line"
- Previous message: Cl?udio: "Re: Breakpoints firing inside mscorwks.dll"
- In reply to: Cl?udio: "Re: Breakpoints firing inside mscorwks.dll"
- Next in thread: Cl?udio: "Re: Breakpoints firing inside mscorwks.dll"
- Reply: Cl?udio: "Re: Breakpoints firing inside mscorwks.dll"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 23 Feb 2005 10:08:42 -0800
sygnosys@gmail.com (Cl?udio) wrote in
news:1ebaeb7c.0502230854.d37f71f@posting.google.com:
> After reading your post I started playing with that switch.
> Originaly it was set to auto and it presents the problem
> described, switching to mixed made some breakpoints sometimes
> work correctly. Finally I switch to managed and the breakpoints
> it started working correctly.
Mixed should work. If it doesn't it's a bug. Switching to managed
will not allow you to step into non-clr compiled sources.
> But I have an interesting/weird thing happening now when
> stepping through the code below. After the first iteration uppon
> returning to the FOR line to evaluate the continuance
> expression, it jumps from the FOR line to the last RETURN S_OK
> line and then returning to the FOR line and then continuing.
> The thing is if I debug it showing the assembly+source code then
> the sequence is normal.
Do you have optimizations turned on? If so, the compiler may be
reordering things for you. If not, then this is a bug with our
line number information. Would you be able to cut this down to a
small application that exhibits the same problem and send it to me
by email?
Thanks,
-- Tarek Madkour, Visual C++ Team This posting is provided "AS IS" with no warranties, and confers no rights.
- Next message: David Liebtag: "Debugging DLL built from command line"
- Previous message: Cl?udio: "Re: Breakpoints firing inside mscorwks.dll"
- In reply to: Cl?udio: "Re: Breakpoints firing inside mscorwks.dll"
- Next in thread: Cl?udio: "Re: Breakpoints firing inside mscorwks.dll"
- Reply: Cl?udio: "Re: Breakpoints firing inside mscorwks.dll"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|