Am 19.02.2012 17:06, schrieb Vladimir Panteleev:
> On Sunday, 19 February 2012 at 15:31:32 UTC, Benjamin Thaut wrote:
>> Which dmd version should I use to build DustMite?
>> I tried 2.055 and 2.058 but DustMite crashes half way through the
>> reductino process without a message (I'm using windows)
>
> I've never heard of a problem like this. Is the DustMite crash
> reproducible?

Yes, it never crashes at the extact same reduction step, but it always crashes somewhere in between. I assume that it is a segfault because it does not print a stack trace. I could however only test it on 1 machine so it could be machine specific.

On Sunday, 19 February 2012 at 16:11:35 UTC, Benjamin Thaut wrote:
> Am 19.02.2012 17:06, schrieb Vladimir Panteleev:
>> On Sunday, 19 February 2012 at 15:31:32 UTC, Benjamin Thaut wrote:
>>> Which dmd version should I use to build DustMite?
>>> I tried 2.055 and 2.058 but DustMite crashes half way through the
>>> reductino process without a message (I'm using windows)
>>
>> I've never heard of a problem like this. Is the DustMite crash
>> reproducible?
>
> Yes, it never crashes at the extact same reduction step, but it always crashes somewhere in between. I assume that it is a segfault because it does not print a stack trace. I could however only test it on 1 machine so it could be machine specific.

I'd appreciate it if you could gather more information about the crash (for example, running in in a debugger so you can get the backtrace of the segfault, if there is one).

Am 19.02.2012 18:25, schrieb Vladimir Panteleev:
> On Sunday, 19 February 2012 at 16:11:35 UTC, Benjamin Thaut wrote:
>> Am 19.02.2012 17:06, schrieb Vladimir Panteleev:
>>> On Sunday, 19 February 2012 at 15:31:32 UTC, Benjamin Thaut wrote:
>>>> Which dmd version should I use to build DustMite?
>>>> I tried 2.055 and 2.058 but DustMite crashes half way through the
>>>> reductino process without a message (I'm using windows)
>>>
>>> I've never heard of a problem like this. Is the DustMite crash
>>> reproducible?
>>
>> Yes, it never crashes at the extact same reduction step, but it always
>> crashes somewhere in between. I assume that it is a segfault because
>> it does not print a stack trace. I could however only test it on 1
>> machine so it could be machine specific.
>
> I'd appreciate it if you could gather more information about the crash
> (for example, running in in a debugger so you can get the backtrace of
> the segfault, if there is one).

rmdirRecurse which gets called in dustmite.d line 457 throws a exception that causes the D exception handler to go into inifnite recursion which leads to a stack overflow and crashes the program.
Might be a issue with my file system. Going to do a file system check.

Kind Regards
Benjamin Thaut

On Sunday, 19 February 2012 at 17:56:42 UTC, Benjamin Thaut wrote:
> rmdirRecurse which gets called in dustmite.d line 457 throws a exception that causes the D exception handler to go into inifnite recursion which leads to a stack overflow and crashes the program.
> Might be a issue with my file system. Going to do a file system check.

One of the reasons that rmdirRecurse might fail is if a program has opened the directory or one of the files. This may be caused by trying to peek at Dustmite's results while it's running without pausing it, or perhaps antivirus/antimalware software.

On Sunday, 19 February 2012 at 17:56:42 UTC, Benjamin Thaut wrote:
> rmdirRecurse which gets called in dustmite.d line 457 throws a exception that causes the D exception handler to go into inifnite recursion which leads to a stack overflow and crashes the program.

Thanks for taking the time to figure this out. I'll make DustMite catch rmdirRecurse failures and retry the operation (as the causes are usually temporary).

Am 19.02.2012 17:06, schrieb Vladimir Panteleev:
> On Sunday, 19 February 2012 at 15:31:32 UTC, Benjamin Thaut wrote:
>> Which dmd version should I use to build DustMite?
>> I tried 2.055 and 2.058 but DustMite crashes half way through the
>> reductino process without a message (I'm using windows)
>
> I've never heard of a problem like this. Is the DustMite crash
> reproducible?

I've made the experience that it is more-or-less impossible to run dustmite on windows for longer time spans. The cause is most probably Windows Explorer, which sometimes accesses and locks files.

In a project we wrote a limited retry-loop around the critical file system calls to get stable runs...

On Sunday, 19 February 2012 at 22:46:29 UTC, Sönke Ludwig wrote:
> Am 19.02.2012 17:06, schrieb Vladimir Panteleev:
>> On Sunday, 19 February 2012 at 15:31:32 UTC, Benjamin Thaut wrote:
>>> Which dmd version should I use to build DustMite?
>>> I tried 2.055 and 2.058 but DustMite crashes half way through the
>>> reductino process without a message (I'm using windows)
>>
>> I've never heard of a problem like this. Is the DustMite crash
>> reproducible?
>
> I've made the experience that it is more-or-less impossible to run dustmite on windows for longer time spans. The cause is most probably Windows Explorer, which sometimes accesses and locks files.
>
> In a project we wrote a limited retry-loop around the critical file system calls to get stable runs...

I've never encountered such problems. DustMite can run for days on end without issues.

Am 20.02.2012 01:40, schrieb Vladimir Panteleev:
> On Sunday, 19 February 2012 at 22:46:29 UTC, Sönke Ludwig wrote:
>> Am 19.02.2012 17:06, schrieb Vladimir Panteleev:
>>> On Sunday, 19 February 2012 at 15:31:32 UTC, Benjamin Thaut wrote:
>>>> Which dmd version should I use to build DustMite?
>>>> I tried 2.055 and 2.058 but DustMite crashes half way through the
>>>> reductino process without a message (I'm using windows)
>>>
>>> I've never heard of a problem like this. Is the DustMite crash
>>> reproducible?
>>
>> I've made the experience that it is more-or-less impossible to run
>> dustmite on windows for longer time spans. The cause is most probably
>> Windows Explorer, which sometimes accesses and locks files.
>>
>> In a project we wrote a limited retry-loop around the critical file
>> system calls to get stable runs...
>
> I've never encountered such problems. DustMite can run for days on end
> without issues.

If I run it inside my C:\Users\<my username>\Documents directory it does not wrong very long. 10 mins max before it crashes. Now I put my sourcecode directly in the root of a partition F:\ and it works just fine without crashing once in hours.

Kind Regards
Benjamin Thaut

On Sunday, 19 February 2012 at 21:42:17 UTC, Vladimir Panteleev wrote:
> On Sunday, 19 February 2012 at 17:56:42 UTC, Benjamin Thaut wrote:
>> rmdirRecurse which gets called in dustmite.d line 457 throws a exception that causes the D exception handler to go into inifnite recursion which leads to a stack overflow and crashes the program.
>
> Thanks for taking the time to figure this out. I'll make DustMite catch rmdirRecurse failures and retry the operation (as the causes are usually temporary).

https://github.com/CyberShadow/DustMite/commit/e2d91dab03b7c98dfbacbbc41f7cf49d3935fd35