debugging log engine build request

[Bernard Devlin]

I sent a whole series of crash logs through RQCC back in August, and was
told they were inconclusive.  I assumed these crash logs were actually
_Windows_ crash logs not Rev crash logs.  I seem to remember some discussion
between you and Eric Chatonet where he was reluctant to send them because
they were encrypted.  I think you talked to the Rev developers who told you
they were Visual Studio crash logs. My understanding is that these logs do
not even exist in the Linux build at all.

If I'm not mistaken then I'm asking for something completely different.  I'm
asking for something that would be equivalent to a 'replay log', so that the
Rev developers could see exactly what was going on inside the engine as the
engine changes state before a crash.

Bernard

On Mon, Sep 29, 2008 at 4:03 PM, J. Landman Gay <jacque at hyperactivesw.com>wrote:

> Bernard Devlin wrote:
>
>> Since I've been having unpredictable but frequent crashes of Revolution
>> 2.9
>> on Vista for the past 4 months, and now daily crashes of Revolution 3.0 on
>> Vista and Linux, I've entered an enhancement request that the engine be
>> modified to include a debug-logging facility (logging messages, property
>> changes, and function calls).
>>
>
> This already exists in the Preferences. In the General pane, look for the
> popdown called "Crash reporting on Windows XP". The default setting is small
> but you can set it to medium (which is actually pretty large.) The resulting
> log will not be human-readable, but the engineers can use it to debug your
> crashes.
>
> --
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>