Hi Jacqueline, I wasn't looking to turn this thread around into looking at the specific problems I had with Rev 2.9-3.0 in June to October 2008. I tried all manner of logging, and even sent multiple crash logs to runrev.com. None of the information that I could get could lead to any indication of the causes of the crashes. In the end I gave up on using Rev on Windows and Linux and just use it on OS X.
I think that in order to solve difficult unreproduceable problems like Camm29 is referring to, we need to have debug logging built into the engine. In the cases I was suffering from, even having debugging built into the the runtime would not help, as Rev was crashing (apparently) randomly. Bernard On 1/23/09, J. Landman Gay <[email protected]> wrote: > Bernard Devlin wrote: >> Perhaps this is another instance where a debug-logging engine would >> produce >> information that would lead to a speedier identification of the problem? >> http://quality.runrev.com/qacenter/show_bug.cgi?id=7237 > > What I'd really like to see is the debugger built directly into the > engine so that we could use a keyboard combination to break into the > debugger during runtime. > > At any rate, did you try turning on Windows crash reporting in prefs? I > think that's supposed to provide the info your enhancement addresses. > > -- > Jacqueline Landman Gay | [email protected] > HyperActive Software | http://www.hyperactivesw.com > _______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
