> But it's not a bug. Like Ali said:
>
> The destruction order of GC-maintained resources is not deterministic as
> e.g. in C++. It is quite possible that the member of an object is destroyed
> before the object itself.
Oops. I get it now.
What should be done to avoid this situation? I think I n
12/3/2012 12:56 PM, d coder пишет:
1) DustMite a tool which allows to automatically reduce test cases.
It has been used with success several times here.
Awesome!
The tool took some 2 hours to reduce my testcase to less than 50 lines.
I have filed a regression.
http://d.puremagic.com/
On Sunday, 2 December 2012 at 04:45:13 UTC, d coder wrote:
Greetings
I have a code that crashes with current github dmd snapshot
with a
segfault. It compiles and runs fine with the released versions
of DMD. I am
using lots of structs and classes in the code and I believe the
problem
could be
On Sunday, 2 December 2012 at 04:45:13 UTC, d coder wrote:
Greetings
I have a code that crashes with current github dmd snapshot
with a
segfault. It compiles and runs fine with the released versions
of DMD. I am
using lots of structs and classes in the code and I believe the
problem
could be
On 12/01/2012 08:44 PM, d coder wrote:
> ==4453== Invalid read of size 8
> ==4453==at 0x44EFF5: _D4nett5mule5Mule3esl6__dtorMFZv
> (../src/nett/mule.d:115)
Are you accessing any resource in Mule's destructor, which is maintained
by the GC? If so, it is possible that that resource has alread
On Sunday, December 02, 2012 10:14:16 d coder wrote:
> Greetings
>
> I have a code that crashes with current github dmd snapshot with a
> segfault. It compiles and runs fine with the released versions of DMD. I am
> using lots of structs and classes in the code and I believe the problem
> could be
