[Issue 5517] SEGV: assert(false) in release mode

2020-03-20 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5517 Basile-z changed: What|Removed |Added CC|b2.t...@gmx.com | --

[Issue 5517] SEGV: assert(false) in release mode

2019-06-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5517 Basile-z changed: What|Removed |Added Status|REOPENED|RESOLVED CC|

[Issue 5517] SEGV: assert(false) in release mode

2015-07-24 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5517 --- Comment #16 from Kenji Hara --- (In reply to Shachar Shemesh from comment #14) > But it is not printing the message. Recently I opened a PR to update core language specifications. https://github.com/D-Programming-Language/dlang.org/pull/1040 In

[Issue 5517] SEGV: assert(false) in release mode

2015-06-28 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5517 --- Comment #15 from Jonathan M Davis --- (In reply to Shachar Shemesh from comment #14) > (In reply to Jonathan M Davis from comment #13) > > Either way, it's killing the program like it's supposed to. > > But it is not printing the message. > > An

[Issue 5517] SEGV: assert(false) in release mode

2015-06-27 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5517 --- Comment #14 from Shachar Shemesh --- (In reply to Jonathan M Davis from comment #13) > Either way, it's killing the program like it's supposed to. But it is not printing the message. Yes, I think the spec is wrong (and, at least when opening a n

[Issue 5517] SEGV: assert(false) in release mode

2015-06-27 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5517 --- Comment #13 from Jonathan M Davis --- On a side note, I just tried this on FreeBSD with -release, and I get a "bus error" rather than a segmentation fault, so the behavior there is slightly different from Linux, if that matters at all. Either way,

[Issue 5517] SEGV: assert(false) in release mode

2015-06-27 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5517 --- Comment #12 from Jonathan M Davis --- (In reply to Shachar Shemesh from comment #11) > Quoth the same spec: > void main() > { > assert(0, "an" ~ "error message"); > } > > When compiled and run, it will produce the message: > Error: AssertError

[Issue 5517] SEGV: assert(false) in release mode

2015-06-25 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5517 Shachar Shemesh changed: What|Removed |Added Status|RESOLVED|REOPENED CC|

[Issue 5517] SEGV: assert(false) in release mode

2015-06-09 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5517 Andrei Alexandrescu changed: What|Removed |Added Version|D1 & D2 |D2 --

[Issue 5517] SEGV: assert(false) in release mode

2013-03-01 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5517 Alexander Tankeev changed: What|Removed |Added CC||atank...@gmail.com --- Comment #10

[Issue 5517] SEGV: assert(false) in release mode

2012-01-28 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5517 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 5517] SEGV: assert(false) in release mode

2011-03-09 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5517 --- Comment #8 from Iain Buclaw 2011-03-09 12:10:47 PST --- Some notes: - sigaction can be used to catch signals - signals caught have a packed struct with some simple information attached. - si_signo: Signal number (ie: SIGSEGV = 11). - si_

[Issue 5517] SEGV: assert(false) in release mode

2011-03-06 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5517 Jonathan M Davis changed: What|Removed |Added CC||jmdavisp...@gmx.com --- Comment #7

[Issue 5517] SEGV: assert(false) in release mode

2011-03-06 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5517 --- Comment #6 from Don 2011-03-06 07:49:39 PST --- (In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > (In reply to comment #2) > > > > Some further detail: 0xF4, the HLT opcode, is a privileged instruction;

[Issue 5517] SEGV: assert(false) in release mode

2011-03-06 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5517 --- Comment #5 from Iain Buclaw 2011-03-06 04:49:31 PST --- (In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > > > Some further detail: 0xF4, the HLT opcode, is a privileged instruction; it > > > doesn't actually

[Issue 5517] SEGV: assert(false) in release mode

2011-03-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5517 --- Comment #4 from Don 2011-03-05 18:28:56 PST --- (In reply to comment #3) > (In reply to comment #2) > > Some further detail: 0xF4, the HLT opcode, is a privileged instruction; it > > doesn't actually get executed. Instead, a Privileged Inst

[Issue 5517] SEGV: assert(false) in release mode

2011-03-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5517 --- Comment #3 from Iain Buclaw 2011-03-05 05:09:41 PST --- (In reply to comment #2) > Some further detail: 0xF4, the HLT opcode, is a privileged instruction; it > doesn't actually get executed. Instead, a Privileged Instruction hardware > exce

[Issue 5517] SEGV: assert(false) in release mode

2011-03-03 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5517 --- Comment #2 from Don 2011-03-03 23:46:40 PST --- Some further detail: 0xF4, the HLT opcode, is a privileged instruction; it doesn't actually get executed. Instead, a Privileged Instruction hardware exception is raised. I would expect Linux t

[Issue 5517] SEGV: assert(false) in release mode

2011-03-02 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5517 Don changed: What|Removed |Added CC||clugd...@yahoo.com.au Component|DMD