Cool. Does the Visualizer use a standard threading
diagramming notation?
peter: not at the moment.
got good links for examples?
Oh, no, that would never work. The gradient is all
wrong, and those arrows are like so 90's.
Seriously though: this is mega-cool, and could really
become a revolutionary new must-have item in the modern
programmer's toolbox.
The challenge now is to make the diagrams clear and
understandable when the racing scenarios get more
complex - maybe even interactive so you can dive in for
details like method names etc.
Also, do you have any easy way to get a visualization of
a racing scenario whenever Racer finds it, or does one
have to re-run the test with the "try this permutation
first" attribute and then visualize?
avish:
when a deadlock or other problem is found in a test, the
visualization image of the thread state is saved and
shown as a clickable link in the output window so you
don't have to re-run the see the visualization.
Making it interactive is the direction, I agree. it also
need to be much nicer looking and understandable.
since we do incremental work, this should get better and
better on the nightly builds and in the stable
(bi-weekly) builds. both build types are available on
the site and I want more feedback like yours.