Can anyone reproduce this?

On my machine, the following program causes an access violation in druntime instead of throwing an AssertError. module test; void foo(int x){assert(x);} void main(){foo(0);} dmd -run test -- killed by signal 11 Is this a regression or a problem with my setup (DMD 2.057 on Ubuntu 11.10 64 bit)? Can anyone reproduce this?

On Sun, Jan 1, 2012 at 7:51 PM, Timon Gehr <timon.gehr@gmx.ch> wrote: > On my machine, the following program causes an access violation in druntime instead of throwing an AssertError. > > module test; > void foo(int x){assert(x);} > void main(){foo(0);} > > dmd -run test > -- killed by signal 11 > > > Is this a regression or a problem with my setup (DMD 2.057 on Ubuntu 11.10 > 64 bit)? > Can anyone reproduce this? > mine throws an AssertError. DMD 2.057, Ubuntu 11.10 64bit

Am 02.01.2012 02:51, schrieb Timon Gehr: > On my machine, the following program causes an access violation in > druntime instead of throwing an AssertError. > > module test; > void foo(int x){assert(x);} > void main(){foo(0);} > > dmd -run test > -- killed by signal 11 > > > Is this a regression or a problem with my setup (DMD 2.057 on Ubuntu > 11.10 64 bit)? > Can anyone reproduce this? Seems like an 64 bit error. On my Ubuntu 11.10 machine (32bit) with the same dmd version, it "works" as expected.

Am 02.01.2012 03:07, schrieb Joshua Reusch: > Am 02.01.2012 02:51, schrieb Timon Gehr: >> On my machine, the following program causes an access violation in >> druntime instead of throwing an AssertError. >> >> module test; >> void foo(int x){assert(x);} >> void main(){foo(0);} >> >> dmd -run test >> -- killed by signal 11 >> >> >> Is this a regression or a problem with my setup (DMD 2.057 on Ubuntu >> 11.10 64 bit)? >> Can anyone reproduce this? > > Seems like an 64 bit error. On my Ubuntu 11.10 machine (32bit) with the > same dmd version, it "works" as expected. Ok, after Caligo: no 64 bit error ...

On Sun, Jan 1, 2012 at 8:07 PM, Joshua Reusch <yoschi@arkandos.de> wrote: > Am 02.01.2012 02:51, schrieb Timon Gehr: > > On my machine, the following program causes an access violation in >> druntime instead of throwing an AssertError. >> >> module test; >> void foo(int x){assert(x);} >> void main(){foo(0);} >> >> dmd -run test >> -- killed by signal 11 >> >> >> Is this a regression or a problem with my setup (DMD 2.057 on Ubuntu >> 11.10 64 bit)? >> Can anyone reproduce this? >> > > Seems like an 64 bit error. On my Ubuntu 11.10 machine (32bit) with the same dmd version, it "works" as expected. > I have the same exact setup as the OP, and mine works as expected, too. Doesn't seem like a 64-bit issue.

On 01/02/2012 03:02 AM, Caligo wrote: > > > On Sun, Jan 1, 2012 at 7:51 PM, Timon Gehr <timon.gehr@gmx.ch > <mailto:timon.gehr@gmx.ch>> wrote: > > On my machine, the following program causes an access violation in > druntime instead of throwing an AssertError. > > module test; > void foo(int x){assert(x);} > void main(){foo(0);} > > dmd -run test > -- killed by signal 11 > > > Is this a regression or a problem with my setup (DMD 2.057 on Ubuntu > 11.10 64 bit)? > Can anyone reproduce this? > > > mine throws an AssertError. > > DMD 2.057, Ubuntu 11.10 64bit Ok, thank you. I wonder what might cause this... I have the same issue with the following program with the -m32 flag. With -m64 it terminates normally instead of throwing. void main(){throw new Throwable("moo");}

On 2 January 2012 02:51, Timon Gehr <timon.gehr@gmx.ch> wrote: > Is this a regression or a problem with my setup (DMD 2.057 on Ubuntu 11.10 > 64 bit)? > Can anyone reproduce this? > I get an assert error. Using DMD 2.057 and Arch Linux, but on 32 bit. So I assume that might be it?