Understanding Crash Log (Real Studio network user group Mailinglist archive)

Back to the thread list
Previous thread: scripting the IDE (was Re: Is it possible...)
Next thread: Shell exceptions


[OT] more Carbon shared library tales   -   Hadley, Joshua
  Understanding Crash Log   -   Lists
   Re: Understanding Crash Log   -   Joseph J. Strout
    Re: Understanding Crash Log   -   Lists
     Re: Understanding Crash Log   -   Tony Spencer
   Re: Understanding Crash Log   -   Christian Schmitz
    Re: Understanding Crash Log   -   Lists
     Re: Understanding Crash Log   -   Joseph J. Strout
      Re: Understanding Crash Log   -   Lists

Understanding Crash Log
Date: 13.12.02 19:15 (Fri, 13 Dec 2002 12:15:15 -0600)
From: Lists
Hi all!

I have a few users of my most popular REALbasic-made product (Print Window)
telling me that Print Window is experiencing an unexpected quit just as it
begins its print routines. It's a small number of people (especially
compared to the number of positive reports I have gotten), but it is
worrisome to me because the symptoms are the same.

Two of these users have been kind enough to supply me with crash logs of the
problem, but I'm at a loss on how to read them.

Given a crash log, is there any way for me to even get the faintest idea
where to start looking for the problem and at least determining if something
else on the user's system is causing the problem?

Any help on this would be greatly appreciated. I can supply the crash log to
any interested parties.

Sincerely,

Scott

Re: Understanding Crash Log
Date: 13.12.02 21:51 (Fri, 13 Dec 2002 12:51:43 -0800)
From: Joseph J. Strout
At 12:15 PM -0600 12/13/02, Scott Crick (Lists) wrote:

>Given a crash log, is there any way for me to even get the faintest idea
>where to start looking for the problem and at least determining if something
>else on the user's system is causing the problem?

Not really. Check their OS version; perhaps you'll see that it
always crashes on 10.2.1 or some such. But that's about all I can
suggest.

Cheers,
- Joe

Re: Understanding Crash Log
Date: 13.12.02 22:41 (Fri, 13 Dec 2002 15:41:04 -0600)
From: Lists
On 12/13/02 2:51 PM, "Joseph J. Strout" <<email address removed>> wrote:

> At 12:15 PM -0600 12/13/02, Scott Crick (Lists) wrote:
>
>> Given a crash log, is there any way for me to even get the faintest idea
>> where to start looking for the problem and at least determining if something
>> else on the user's system is causing the problem?
>
> Not really. Check their OS version; perhaps you'll see that it
> always crashes on 10.2.1 or some such. But that's about all I can
> suggest.

Rats. Not what I wanted to hear. ;-)

It doesn't appear to be limited to a specific OS, although the only OS's
that the problem has been reported with is 10.2.1 and 10.2.2.

The only clue I have is that the crash occurs right near the beginning of a
printing routine (that also happens to be threaded). Of course, I can't
reproduce this problem whatsoever. And printer-type doesn't seem to matter.
In these few cases, it happens with both PostScript printers from HP, Xanté
and Brother and inkjets from HP and Epson.

Sincerely,

Scott
-

Re: Understanding Crash Log
Date: 14.12.02 21:56 (Sat, 14 Dec 2002 21:56:43 +0100)
From: Tony Spencer
Hmmm, you're told to submit crash logs because it helps track crashes,
and Joe tells us it ain't so...

I think most users would be capable of reporting their OS version
without sending a crash log!

Anyway, your problem seems that it may be connected to Jaguar, and could
be a possible problem with old or even beta print drivers. Jaguar caused
many problems with all sorts of things. My guess is that maybe these
users have upgraded to Jaguar but not upgraded their print drivers, if
there are any newer ones. I know there's a range of printers there, but
maybe that's the problem. Could be that or the updated Quartz engine in
Jaguar?

There were literally thousands of reports here of Rb apps crashing when
Jaguar first appeared, though since I don't run Jaguar myself, don't
know further.

And the big question is are Apple gonna screw things all up again when
they release 10.3 ?

On Friday, December 13, 2002, at 10:41 pm, Scott Crick (Lists) wrote:

>> Not really. Check their OS version; perhaps you'll see that it
>> always crashes on 10.2.1 or some such. But that's about all I can
>> suggest.
>
> Rats. Not what I wanted to hear. ;-)
>
> It doesn't appear to be limited to a specific OS, although the only OS's
> that the problem has been reported with is 10.2.1 and 10.2.2.
>
> The only clue I have is that the crash occurs right near the beginning
> of a
> printing routine (that also happens to be threaded). Of course, I can't
> reproduce this problem whatsoever. And printer-type doesn't seem to
> matter.
> In these few cases, it happens with both PostScript printers from HP,
> Xanté
> and Brother and inkjets from HP and Epson.

Tony Spencer
St Etienne du Grès, (13) France
<email address removed>
http://homepage.mac.com/tonyspencer/

---
A searchable archive of this list is available at:
<http://dbserver.realsoftware.com/KBDB/search.php>

Unsubscribe:
<mailto:<email address removed>>

Subscribe to the digest:
<mailto:<email address removed>>

Re: Understanding Crash Log
Date: 15.12.02 19:56 (Sun, 15 Dec 2002 19:56:44 +0100)
From: Christian Schmitz
> Hi all!
>
> Given a crash log, is there any way for me to even get the faintest idea
> where to start looking for the problem and at least determining if something
> else on the user's system is causing the problem?

You can look for the name of the function which made the crash.

Mfg
Christian

Re: Understanding Crash Log
Date: 15.12.02 20:10 (Sun, 15 Dec 2002 13:10:48 -0600)
From: Lists
On 12/15/02 12:56 PM, "Christian Schmitz" <<email address removed>>
wrote:

>> Hi all!
>>
>> Given a crash log, is there any way for me to even get the faintest idea
>> where to start looking for the problem and at least determining if something
>> else on the user's system is causing the problem?
>
> You can look for the name of the function which made the crash.

Actually, I discovered the cause of the crash. Default Folder X doesn't play
well with Print Window for some reason. I haven't actually figured out the
actual reason, but when those two users disabled Default Folder X, Print
Window worked like a champ.

Sincerely,

Scott

Re: Understanding Crash Log
Date: 15.12.02 20:53 (Sun, 15 Dec 2002 11:53:11 -0800)
From: Joseph J. Strout
At 1:10 PM -0600 12/15/02, Scott Crick (Lists) wrote:

>Actually, I discovered the cause of the crash. Default Folder X doesn't play
>well with Print Window for some reason. I haven't actually figured out the
>actual reason, but when those two users disabled Default Folder X, Print
>Window worked like a champ.

Make sure they have the latest version of Default Folder X.

Best,
- Joe

Re: Understanding Crash Log
Date: 15.12.02 22:46 (Sun, 15 Dec 2002 15:46:10 -0600)
From: Lists
On 12/15/02 1:53 PM, "Joseph J. Strout" <<email address removed>> wrote:

>> Actually, I discovered the cause of the crash. Default Folder X doesn't play
>> well with Print Window for some reason. I haven't actually figured out the
>> actual reason, but when those two users disabled Default Folder X, Print
>> Window worked like a champ.
>
> Make sure they have the latest version of Default Folder X.

They are using 1.6.4 (which I believe is the latest version).

Sincerely,

Scott