On Monday, September 8, 2003, at 09:54 AM, Chris Sheffield wrote:
If the Rev IDE crashes, is there any way to find out why? Like a log file
or something that is written to?
I'm working on OS X 10.2.6. I've got a main stack that opens another stack
via the go command. I've debugged it and Rev crashes every time on the line
with the go command. I cannot figure out what's going on, and I can't debug
any further because it crashes. I'm not sure if I've got bad code in the
handlers of the new stack or not. But the exact same thing runs fine under
Windows. I've tried placing breakpoints in my preOpenStack and preOpenCard
handlers to no avail. It seems like the go command is actually what's
failing.
Can anyone think of anything else I could check for or do?
File bug with bugzilla, but before doing so, get a crash trace to include in the bug report. Go to Console.app, and in it's prefs turn on crash reporting. This information will be useful for the engine developers, but perhaps useless in terms of your transcript code.
If you include a sample stack and the crash trace then the engine developers should be able to fix it. (the engine or IDE should never crash because of something you do in transcript)
Alex Rice <[EMAIL PROTECTED]> | Mindlube Software | http://mindlube.com
what a waste of thumbs that are opposable to make machines that are disposable -Ani DiFranco
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
