You can open the dump with any visual studio, but to make use of it,
you will need the some files (.pdb?) produced for the particular build
which is crashing on the machine. I am not sure if these files are
available for the nightlies (Jürgen?) but I guess it would be the
easiest thing to compile it on your dev machine, reproduce on the other
machine with your build and then analyze the dump on your dev-machine
again.
Or you just revert to simple printf debugging in your plugin and narrow
down the point of failure with some log messages
(http://docs.python.org/2/library/logging.html).
On Mon 10 Feb 2014 04:42:41 PM CET, Denis Rouzaud wrote:
Thanks Matthias.
Weird, but the debug messages did not lead to anything special.
I will try with the dump, but it seems to be a PIA to be abble to
install the tools to view these dumps...
Thanks again!
Cheers,
Denis
On 10. 02. 14 15:58, Matthias Kuhn wrote:
As you say there is no minidump question: If the process is still
running I think you can right click in the task manager and choose
something like "create dump" or similar. You could also install
debugview to see the last debug messages.
Matthias
On Mon 10 Feb 2014 03:53:47 PM CET, Denis Rouzaud wrote:
Hi all,
I get a crash on a windows machine with a plugin. It is strange as it
seems it does not occur on every machine.
I would like to investigate, but I don't know what info I can get.
Is there a way to know where the crash occurs without any IDE?
PS: I don't get the warning saying there is a minidump. QGIS just
blanks out.
Thanks,
Denis
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
