March 29, 2012
My stacktraces have "changed" a bit...
t.d:
vaid main() {
    assert(false);
}

2.058:
core.exception.AssertError@t(2): Assertion failure
----------------
t(_d_assertm+0x2a) [0x4144be]
t() [0x414492]
t(_Dmain+0xe) [0x414476]
t(extern (C) int rt.dmain2.main(int, char**).void runMain()+0x17) [0x414c93]
t(extern (C) int rt.dmain2.main(int, char**).void tryExec(scope void delegate())+0x2a) [0x41460a]
t(extern (C) int rt.dmain2.main(int, char**).void runAll()+0x42) [0x414ce6]
t(extern (C) int rt.dmain2.main(int, char**).void tryExec(scope void delegate())+0x2a) [0x41460a]
t(main+0xd3) [0x41459b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f2a3f1d030d]
----------------

2.059HEAD:
_d_throw(h = 0x7fbb34781f80, &h = 0x7fffd2231ab8)
	vptr = 0x45a7b0
_d_throw(h = 0x45abd0, &h = 0x7fffd2231078)
	vptr = 0x45ac50
found caller, EBP = 0x7fffd2231090, retaddr = 0x4407fe
FuncTable.sizeof = 0x18
__eh_finddata(address = 0x4407fe)
_deh_beg = 0x45fbc0, _deh_end = 0x460070
	ft = 0x45fbc0, fptr = 0x42dc0c, fsize = x10d, handlertable = 0x661370
	ft = 0x45fbd8, fptr = 0x42dd1c, fsize = x064, handlertable = 0x6613a0
	ft = 0x45fbf0, fptr = 0x4355c4, fsize = x118, handlertable = 0x662ca8
	ft = 0x45fc08, fptr = 0x435788, fsize = x092, handlertable = 0x662cd8
	ft = 0x45fc20, fptr = 0x435ce4, fsize = x0de, handlertable = 0x662d30
(snip)

Tested on linux.

Does anyone else has the same issue, or have I done anything strange in the build process?
March 30, 2012
On Thu, 29 Mar 2012 16:11:47 +0200, simendsjo <simendsjo@gmail.com> wrote:

> My stacktraces have "changed" a bit...
> t.d:
> vaid main() {
>      assert(false);
> }
>
> 2.058:
> core.exception.AssertError@t(2): Assertion failure
> ----------------
> t(_d_assertm+0x2a) [0x4144be]
> t() [0x414492]
> t(_Dmain+0xe) [0x414476]
> t(extern (C) int rt.dmain2.main(int, char**).void runMain()+0x17) [0x414c93]
> t(extern (C) int rt.dmain2.main(int, char**).void tryExec(scope void delegate())+0x2a) [0x41460a]
> t(extern (C) int rt.dmain2.main(int, char**).void runAll()+0x42) [0x414ce6]
> t(extern (C) int rt.dmain2.main(int, char**).void tryExec(scope void delegate())+0x2a) [0x41460a]
> t(main+0xd3) [0x41459b]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f2a3f1d030d]
> ----------------
>
> 2.059HEAD:
> _d_throw(h = 0x7fbb34781f80, &h = 0x7fffd2231ab8)
> 	vptr = 0x45a7b0
> _d_throw(h = 0x45abd0, &h = 0x7fffd2231078)
> 	vptr = 0x45ac50
> found caller, EBP = 0x7fffd2231090, retaddr = 0x4407fe
> FuncTable.sizeof = 0x18
> __eh_finddata(address = 0x4407fe)
> _deh_beg = 0x45fbc0, _deh_end = 0x460070
> 	ft = 0x45fbc0, fptr = 0x42dc0c, fsize = x10d, handlertable = 0x661370
> 	ft = 0x45fbd8, fptr = 0x42dd1c, fsize = x064, handlertable = 0x6613a0
> 	ft = 0x45fbf0, fptr = 0x4355c4, fsize = x118, handlertable = 0x662ca8
> 	ft = 0x45fc08, fptr = 0x435788, fsize = x092, handlertable = 0x662cd8
> 	ft = 0x45fc20, fptr = 0x435ce4, fsize = x0de, handlertable = 0x662d30
> (snip)
>
> Tested on linux.
>
> Does anyone else has the same issue, or have I done anything strange in the build process?

Anyone experiencing the same issue or know why I'm getting this type of trace?