Sorry for the necromancy.
I failed to reproduce the issue for single threaded programs.
Which is good.
As far as std.concurrency is concerned I still have questions.
1. How does the main thread of a program print an
(Assert)Error/Exception when it is terminated by it ?
2. Where is the
On Tuesday, 7 June 2016 at 04:21:34 UTC, Mike Parker wrote:
On Tuesday, 7 June 2016 at 02:05:00 UTC, Seb wrote:
On Tuesday, 7 June 2016 at 01:40:01 UTC, your_name wrote:
The way I traced the problem, ironically ;), was to catch
Error and print it to screen.
It involved dereferencing a null
On Tuesday, 7 June 2016 at 02:05:00 UTC, Seb wrote:
On Tuesday, 7 June 2016 at 01:40:01 UTC, your_name wrote:
The way I traced the problem, ironically ;), was to catch
Error and print it to screen.
It involved dereferencing a null pointer in a thread and an
'assert null this' silently killed
On Tuesday, 7 June 2016 at 01:40:01 UTC, your_name wrote:
On Monday, 6 June 2016 at 00:09:15 UTC, Ali Çehreli wrote:
[...]
Hello Ali,
The behavior you described is what I'd expect, however, it's
not what I get.
The way I traced the problem, ironically ;), was to catch Error
and print it
On Monday, 6 June 2016 at 00:09:15 UTC, Ali Çehreli wrote:
On 06/05/2016 07:39 AM, your_name wrote:
> The problem I have is whenever an assert in my debug build
fails the
> program or thread is just killed silently.
That's strange. When an assertion fails, the stack trace is
printed and the
On 06/05/2016 07:39 AM, your_name wrote:
> The problem I have is whenever an assert in my debug build fails the
> program or thread is just killed silently.
That's strange. When an assertion fails, the stack trace is printed and
the program is terminated. For example:
void fun(int i) {
Hello,
thanks for reading this.
The problem I have is whenever an assert in my debug build fails
the program or thread is just killed silently.
How can I change this behavior to something akin to SIGSEGV ?
Thanks!
