https://issues.dlang.org/show_bug.cgi?id=7349
--- Comment #6 from Walter Bright ---
The offending code:
https://github.com/dlang/druntime/blob/f94e816c1dd229cbb133085a6fc41d1bd6d45594/src/core/exception.d#L417-L449
Andrei suggests using a thread local static object to throw.
--
https://issues.dlang.org/show_bug.cgi?id=7349
--- Comment #7 from Walter Bright ---
https://github.com/dlang/druntime/pull/1710
--
https://issues.dlang.org/show_bug.cgi?id=7349
thomas.bock...@gmail.com changed:
What|Removed |Added
CC||thomas.bock...@gmail.com
--- Commen
https://issues.dlang.org/show_bug.cgi?id=7349
Mathias LANG changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
http://d.puremagic.com/issues/show_bug.cgi?id=7349
SomeDude changed:
What|Removed |Added
CC||lovelyd...@mailmetrash.com
Severit
https://issues.dlang.org/show_bug.cgi?id=7349
--- Comment #1 from joa...@airpost.net ---
Is this a bug or is it not allowed to assert in a destructor? I ran into this
while running the druntime tests on Android/x86, was very annoying as the
assert in core.sync.semaphore was swallowed up by the
In
https://issues.dlang.org/show_bug.cgi?id=7349
safety0ff.bugz changed:
What|Removed |Added
CC||safety0ff.b...@gmail.com
--- Comment #2 from
https://issues.dlang.org/show_bug.cgi?id=7349
--- Comment #3 from Joakim ---
(In reply to safety0ff.bugz from comment #2)
> The current GC does not support allocation during destruction (quality of
> implementation issue.)
> When the assert fails and tries to allocate it causes an invalid memory
https://issues.dlang.org/show_bug.cgi?id=7349
Walter Bright changed:
What|Removed |Added
CC||bugzi...@digitalmars.com
--- Comment #4 from
https://issues.dlang.org/show_bug.cgi?id=7349
Sobirari Muhomori changed:
What|Removed |Added
CC||matt.elk...@gmail.com
--- Comment #5 from
10 matches
Mail list logo