If you want to figure out EXACTLY where the crash occurs, I have a
suggestion:
Download the Carbon Declare Library (http://www.tildesoft.com)
Then go to the close event of every window (and the destructor of any
objects accessed in said close events) and put a WriteToLog call
specifying the location before and after any code which might possibly
trigger the crash, including the last line in every event. (you might
want to start with just the first and last lines of each event)
Run the program until it crashes.
Look at the console log. The last line in it will be the last
WriteToLog call executed. Go back to that area, and if you need to, add
more calls to narrow the area down more, then run until crash again.
This way you can determine the specific line of code it crashes on, and
if it crashes on the same line every time.
HTH,
Kevin
On Friday, October 25, 2002, at 06:36 PM, Tim James wrote:
Your comments on destructors etc seem on the money. I have msgboxed
all the close events of the objects and the window close event. It is
after this that the crash occurs. Also have commented out all the
object event code except for the key down that causes the self.close.
No good.
--
Kevin Ballard
kevin at sb dot org
http://www.tildesoft.com
Email from Korea or China must go to <kevin dot nb at sb dot org>
---
A searchable archive of this list is available at:
<http://dbserver.realsoftware.com/KBDB/search.php>
Unsubscribe:
<mailto:realbasic-betas-off at lists dot realsoftware dot com>
Subscribe to the digest:
<mailto:realbasic-betas-digest at lists dot realsoftware dot com>
.
|