[Issue 4385] Uncaught exceptions should call abort() at the place where the exception was thrown

2016-04-07 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=4385

Marenz  changed:

   What|Removed |Added

   See Also||https://issues.dlang.org/sh
   ||ow_bug.cgi?id=15895

--

[Issue 4385] Uncaught exceptions should call abort() at the place where the exception was thrown

2016-04-07 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=4385

Marenz  changed:

   What|Removed |Added

 CC||dmdtrac...@supradigital.org

--- Comment #7 from Marenz  ---
Reading this, https://issues.dlang.org/show_bug.cgi?id=15894 and
https://issues.dlang.org/show_bug.cgi?id=15895 are probably related as well.

--

[Issue 4385] Uncaught exceptions should call abort() at the place where the exception was thrown

2016-04-07 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=4385

Marenz  changed:

   What|Removed |Added

   See Also||https://issues.dlang.org/sh
   ||ow_bug.cgi?id=15894

--

[Issue 4385] Uncaught exceptions should call abort() at the place where the exception was thrown

2016-04-06 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=4385

Vladimir Panteleev  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||thecybersha...@gmail.com
 Resolution|--- |WORKSFORME

--- Comment #6 from Vladimir Panteleev  ---
I think this is already possible by setting rt_trapExceptions=0 (BEFORE the
runtime is initialized, i.e. from a debugger), then breakpointing abort() /
rt.deh_win64_posix.terminate() / etc. Reopen if this is still an issue. I've
filed a related issue 15886.

--

[Issue 4385] Uncaught exceptions should call abort() at the place where the exception was thrown

2016-04-06 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=4385

Vladimir Panteleev  changed:

   What|Removed |Added

   See Also||https://issues.dlang.org/sh
   ||ow_bug.cgi?id=15886

--

[Issue 4385] Uncaught exceptions should call abort() at the place where the exception was thrown

2015-06-09 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=4385

Andrei Alexandrescu  changed:

   What|Removed |Added

Version|D1 & D2 |D2

--

[Issue 4385] Uncaught exceptions should call abort() at the place where the exception was thrown

2011-12-22 Thread d-bugmail 
http://d.puremagic.com/issues/show_bug.cgi?id=4385



--- Comment #5 from Leandro Lucarella  2011-12-22 15:37:17 
PST ---
FYI I have it working perfectly in Tango/D1 (I even print a stack trace). If
you're interested I can share the code.

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

[Issue 4385] Uncaught exceptions should call abort() at the place where the exception was thrown

2010-08-03 Thread d-bugmail 
http://d.puremagic.com/issues/show_bug.cgi?id=4385



--- Comment #4 from Sobirari Muhomori  2010-08-03 
20:13:11 PDT ---
Why not call abort from onAssertError function?

(In reply to comment #2)
> What I don't get is why this works with
> object dtors that are run as the stack unwinds though.

If I remember it correctly, objects are destructed during the catch phase. I
think, this won't work with sjlj exceptions.

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