10 Nov
2014
10 Nov
'14
9:49 p.m.
On Mon, 10 Nov 2014 22:29:52 +0100
Carsten Kurz <audiovisual(a)t-online.de> wrote:
Am 10.11.2014 um 00:34 schrieb Carl Hetherington:
It's almost certainly an uncaught exception or other error in
DCP-o-matic, and probably nothing to do with Visual C++ (it's not even
built with Visual C++, it's just using its runtime libraries AFAICT).
It's just hard to get at the root cause on Windows... the hacks in
1.76.12 might help if the crash is repeatable (with luck, the
backtrace.txt file gives clues as to what was happening when it
crashed).
Regards,
Carl
Strange. 1.76.12 also has slightly improved error reporting in
that it might (I'm not sure) drop a file called "backtrace.txt"
into the film's directory when that crash occurs. That file might
be useful for me to look at. The log file would also be good, if
that's available.
I don't know if that Visual C++ error message is a clear hint towards
VC++ as the source of the problem - but, I have never seen any
special prerequisites regarding this library for DCP-o-matic. I
notice that my WIN7-64Pro Laptop has a couple of them installed -
2005 WIN32+WIN64, 2008 with various version numbers, etc. I can see
there are more recent versions of it available on the net for
download.