Bernard Devlin wrote:
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.

They're Rev crash logs, the actual Windows logs can be accessed from Dr Watson (at least in XP, not sure about Vista.) I believe the Rev crash logs do show the various machine states as Rev executes commands.

 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.

Right, I don't think there's any logging for Linux. I thought you mentioned that the crash happened on both Windows and Linux though, and I was hoping the Windows logs would give a clue to the problem on both.


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.

I think that's what the Rev logs do mostly, if you have the software to read them. But if you have any other logging tools, the more the better. Go for it.

Are you by chance working a lot with images? I had a severe series of crashes in a current project on both 2.9 and 3.0 which turned out to be image-related, particularly when manipulating large images (there's a bug report about that.) I sent the team my stack and it blew up for them on demand. I have a scripted work-around for my particular situation.

I've forgotten if you said you sent them your stack, but I've found that's the most reliable way to get things fixed, especially if the crash log is inconclusive.

--
Jacqueline Landman Gay         |     [EMAIL PROTECTED]
HyperActive Software           |     http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to