![]() |
![]() ![]() |
![]() |
![]()
Post
#1
|
|
![]() Administrator ![]() ![]() ![]() Group: Admin Posts: 168 Joined: 2-May 03 From: New Hampshire Member No.: 1 ![]() |
Now that Savitar is in beta again, there stands a chance you may have an occasional unexpected crash.
If you are running on Mac OS X, it is immensely useful to email the crash log along with your bug report. What's a crash log? It's information that Mac OS X writes to the Console. You can enable crash logs by going to the Console application (located in /Applications/Utilities/) and selecting the "enable crash logs" in the "Crashes" tab of the Console app's preferences. You can also enable "automatically display crash logs" which will make it really easy for you to copy/paste the log to a Savitar bug report email. Search Mac OS X help for "crash log" for more info. Thanks! /Jay |
|
|
Guest_jhersh_* |
![]()
Post
#2
|
Guests ![]() |
Upon launching version 1.3 beta 2... (This is my crash log)
--------------------------------------------------------------------------- "Savitar 1.3b2" debug log for Sun, May 4, 2003 3:26:35 AM --------------------------------------------------------------------------- EXCEPTION THROWN - ERROR: -43, FUNCTION: PreprocessMenu, FILE: LDebugMenuAttachment.cp, LINE: 574 --------------------------------------------------------------------------- "Savitar 1.3b2" debug log for Sun, May 4, 2003 3:26:37 AM --------------------------------------------------------------------------- SIGNAL RAISED - CONDITION: App Initialization failed., FUNCTION: Run, FILE: LApplication.cp, LINE: 213 There was one error immediately after the other, then the program quit itself. |
|
|
![]()
Post
#3
|
|
![]() Administrator ![]() ![]() ![]() Group: Admin Posts: 168 Joined: 2-May 03 From: New Hampshire Member No.: 1 ![]() |
The bug reported by jhersh is fixed in Savitar 1.3b3.
/jay |
|
|
![]() ![]() |
Lo-Fi Version | Time is now: 25th August 2024 - 02:23 PM |