Well, as i explained in the other thread, debugvtk was your only option. You could also read the values of the dofs in the *.out file and write your own postprocessing tool in matlab/python.
Looks like you opened the standard VTU file. The debugvtk option writes lots of small VTK file and doesn't influence the VTU files or any other export modules.
As the name indicates, this is for debugging purposes, so it is very rudimentary and not a very convenient way of visualizing it, but i just tried it out and it seems the crack is exported.