Dustmite always reduced to empty set after two iterations
Nordlöw
per.nordlow at gmail.com
Wed Oct 11 20:36:58 UTC 2017
Once again I need to pick up Dustmite to track down a DMD and LDC
ICE in release mode for my project. But I can't figure out how
call Dustmite correctly:
When I build https://github.com/nordlow/phobos-next as
/usr/bin/dub build --compiler=dmd --build=release
it prints
Performing "release" build using dmd for x86_64.
phobos-next 0.2.0+commit.1570.gec0578b0: building
configuration "library"...
to stdout and
Segmentation fault (core dumped)
dmd failed with exit code 139.
to stderr, along with a (dub) exit status code 2.
My first idea is to make stderr "core dumped" the invariant.
Therefore my first try becomes to redirect stderr to stdout (in
bash) and grep for the pattern 'core dumped' as follows
dustmite src "/usr/bin/dub build --root=.. --compiler=dmd
--build=release 2>&1| grep 'core dumped'"
But this gets reduced to empty set as follows
...
Loading src/zio.d
None => Yes
############### ITERATION 0 ################
============= Depth 0 =============
[ 0.0%] Remove [] => Yes
Done in 2 tests and 12 secs and 653 ms; reduced to empty set
I've also tried adding the flag
--no-redirect
but then I instead get
...
Loading src/zio.d
None => Segmentation fault (core dumped)
Yes
############### ITERATION 0 ################
============= Depth 0 =============
[ 0.0%] Remove [] => Segmentation fault (core dumped)
Yes
Done in 2 tests and 11 secs and 122 ms; reduced to empty set
What am I doing wrong?
More information about the Digitalmars-d-learn
mailing list