RUNREV Technical support
bdrunrev at gmail.com
Fri Jan 23 17:03:14 EST 2009
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
On 1/23/09, J. Landman Gay <jacque at hyperactivesw.com> wrote:
> Bernard Devlin wrote:
>> Perhaps this is another instance where a debug-logging engine would
>> information that would lead to a speedier identification of the problem?
> 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 | 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
More information about the Use-livecode