[Issue 11549] Throwing an exception while debugging causes incorrect execution

d-bugmail at puremagic.com d-bugmail at puremagic.com
Sun Nov 24 10:01:10 PST 2013


https://d.puremagic.com/issues/show_bug.cgi?id=11549



--- Comment #3 from Rainer Schuetze <r.sagitario at gmx.de> 2013-11-24 10:01:06 PST ---
I just tried it again with the example referenced by issue 11033: it just works
for me.

What you describe for mago is what happens when you press "ignore", but that is
expected behaviour. The same holds for answering "no" to the "Pass exception on
to program being debugged?" question when continuing after stopping at the
exception. Do these options behave identically for you?

Regarding stopping on specific exceptions: if you want to treat an exception
differently than others, it must be added explicitely to the list of
exceptions, e.g. as "main.WLServException". Mago doesn't check base classes of
an unlisted exception.

>I'm using VS2010, so I guess that option doesn't apply?

Yes, it is only for VS2012 and later.

>I have all D Exceptions unchecked. I don't want it to break on exceptions at
>all, but I can't seem to control it with those options.

The "D Exceptions" top level entry is only for mago, disabling this root entry
and all sub-entries should work. 
The VS debug engine interprets D's exceptions as Win32 Exceptions, so you'll
have to disable entry 0xe0440001.

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------


More information about the Digitalmars-d-bugs mailing list