You can always provide the crash logs from the Mac OS X crash reporter. The log can be found at:
~/Library/Logs/CrashReporter/Camino.crash.log
When submitting, provide a brief description of what you were doing at the time to give the developer a bit of a clue as to where to look for the problem.
HTH
Regards, Aaron
On Mar 26, 2004, at 9:13 AM, paulc wrote:
At 12:04 PM -0500 3/26/04, [EMAIL PROTECTED] supposedly scribed:
Yes yes yes, this is on my list. The reason wasn't laziness or because I wanted to play with icons, it was because we didn't have access to the talkback server that mozilla was using to upload the symbols used to decipher the reports.
I've been working with the mozilla foundation to get this handled, but it's been slow going. They only *last week* got it working again for seamonkey and firefox. Bug [EMAIL PROTECTED] to hook it up for camino. He's the only one who can do it (I do not have access inside their firewall to hook it up).
When hooked up, talkback sends back the full stack as well as being able to line up the crash with a line number in the code. It's quite helpful and a blocker for releasing 0.8
Thanks Mike, didn't mean to sound critical. This random crashing is by far the most serious issue I experience; as I said, if it happened consistently on a specific page then it's a combo of it's code and not so hot trapping in Camino... but it's the 95% that are not consistent that has me "more" concerned, as it's hard to provide feedback.
_______________________________________________
Camino mailing list
[EMAIL PROTECTED]
http://mozdev.org/mailman/listinfo/camino
_______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino
