This is to avoid crashdumps generated by crashdump_viewer, possibly
overwriting the currently analysed crashdump.

* siri/observer/cdv-no-distribution/OTP-14010:
  [observer] Start crashdump_viewer in a non-distributed node

deleted:    priv/crashdump_viewer.tool
deleted:    priv/crashdump_viewer/collapsd.gif
deleted:    priv/crashdump_viewer/exploded.gif

The shell script (priv/bin/cdv) and bat file (priv/bin/cdv.bat) which
can be used for starting crashdump_viewer both started a distributed
erlang node. This would cause any attempt at starting a second
instance of the crashdump_viewer to fail. To solve this problem, cdv
and cdv.bat now use non-distrubuted nodes when starting the
crashdump_viewer.

Some png libs can not read the old images for some reason.

Use observer for the gui part

DC's and GC's is not double buffered by default on windows,
and there is a separate erase event which causes awful flickering
when constant updating a window.

Hack around wx (to be able to use wxBufferPaintDC),
to avoid flickering on windows.

This works on windows because there (and only there)
wxGC:create/1 also takes a memoryDC as argument.

Since browsers no longer can provide the full path of a file selected
with a file-type input field (browse button), the input field for
loading a crashdump is now changed to a plain text input field. Since
this reduces the user-friendlyness, a shell script (and a .bat file)
has instead been added so the crashdump_viewer can be started directly
from the command line - and thus normal tab completion can be used for
selecting the crashdump file.

Usage: cdv file [ browser ]