Previous 1 2 Next 17 Replies Latest reply: Oct 9, 2009 7:10 AM by romad
Alancito Level 6 (11,095 points)
With the release of Snow Leopard there has been a spate of lengthy crash reports being posted inline, making the threads wider and difficult to read. I searched the _User Tips LIbrary_ for a tip on how to post a link to a crash report, but found nothing.

Assuming I haven't overlooked an existing tip for this, there must be several ways to do this — but I wonder about the following...

• Which document format would be best?

• Should the link open in the browser rather than triggering a download?

• One recommendation for MobileMe subscribers and another for others?

 ~ Alancito

 MacBook Pro 15", Mac OS X (10.5.8), MobileMe iLife'08 iWork'08
  • varjak paw Level 10 (169,827 points)
    The only way to post a link to a crash report would be if you hosted the report on a personal web site somewhere in which case you just post a link to that page as you would any other URL. I would not suggest posting any crash report as a document to be downloaded; that's asking a bit much on trust (we have no way of knowing that what purports to be a crash report really is that and only that).

    In general, it's best not to post a crash report at all unless someone asks for one. Most people gain little useful information from a crash report and including one by default just make it difficult for people to read about your problem. If someone asks you to post a crash report, then we just deal with the formatting issue.

  • ~Bee Level 7 (31,425 points)
    Dave --
    I LOVE reading crash reports.
    Well, Safari ones, that is.

    It used to be, several years ago, that is was very rare that crash reports
    were posted. Now, it's more common. I'm not sure about other forums,
    but I have to say, in Safari, the crash report can save hours and hours
    of making suggestions that don't work, and the OP trying 40 different
    WAG guesses.

    I have noticed that over in iChat, Ralph Johns specifically asks for only
    certain parts of the reports.

    Several posts I've noticed recently are uploading them to hosting sites.
    It's just as efficient for us, and it saves those obscenely wide post boxes here.
    Alancito, you've asked a terrific question.


    Message was edited by: ~Bee
  • Tuttle Level 7 (29,470 points)
    Actually, we used to be able to post links to files on people's computers that would open on their machines when clicked. In other words, if you wanted to point out a local file for someone you were helping, you could post a link that looked something like this (this file doesn't actually exist):

    /System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources/ ExampleFile.plist

    written as:

    <a href="file:///System/Library/PrivateFrameworks/DiskManagement.framework/Version s/A/Resources/ExampleFile.plist" target=_blank>/System/Library/PrivateFrameworks/DiskManagement.framework/Versio ns/A/Resources/ExampleFile.plist</a>

    where the link led directly to their /System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources/ ExampleFile.plist, and the file would open on their desktop, which was useful in that you could point them to exactly the line(s) of code they needed to look at while you were working with them.

    That functionality disappeared some time ago because of the potential for malfeasance, but I think it goes in the direction of what you're describing.
  • Alancito Level 6 (11,095 points)
    ~Bee wrote:
    Several posts I've noticed recently are uploading them to hosting sites.

    Bee ~ If you can track them down again, pls link here to some of those posts so I can see what doc type and hosting sites they used. I'm familiar with image hosting sites, but not file hosting sites — except MobileMe and which gives you 100MB of storage free without signing up. ...Perhaps someone can write up a tip for the +User Tips LIbrary+ on how to post a searchable, non-downloaded crash report on or other host.
    ~Bee wrote:
    I LOVE reading crash reports.

    Perhaps I can learn to love them...

    _Tutorial: An introduction to reading Mac OS X crash reports_

    _Mac OS X Reference Library: CrashReporter_
    ~Bee wrote:
    ...40 different WAG guesses.

    With my sheltered upbringing, I had to look up the meaning of WAG — apparently a less than intelligent conjecture of the caliber of a small undomesticated horse-like mammal. ...Sometimes these forums do exhibit that characteristic.

     ~ Alancito
  • ~Bee Level 7 (31,425 points)
    I'll keep an eye out, Alancito.
  • Alancito Level 6 (11,095 points)
    In this Apple +Knowledge Base+ article: _Mac OS X: How to log a kernel panic_ says:

    *Providing the information to Apple*

    If you record a kernel panic, you can post this information to _Apple Discussions_. Please include detailed hardware configuration information in your post. You may do this by copying and pasting information from a System Profiler report into your post. Please also include any reproducible steps that lead to this message. Apple cannot respond to all postings.

    My understanding has been that Apple will not respond to ANY kernel panic postings. If so, as +"Apple Hosts (...) help identify possible content for Apple's Knowledge Base..."+, perhaps a Host can forward this to the appropriate Apple group for correction.

     ~ Alancito
  • a brody Level 9 (65,743 points)
    Apple may not be able to respond, but engineers may decide to read Discussions from time to time without informing users. Apple does have mechanisms for software developers to report bugs, i.e. signup for an online developer account

    and login here:

    Naturally you will usually be under nondisclosure if you report there.


    where you get no direct feedback from Apple, except rarely.

    I do agree though, only post said crash reports when asked.

    Many crash reports you get an opportunity to "Send to Apple" directly from your computer without going through a web browser.

    If you start your own thread with a kernel panic log, expect few others to be able to respond, simply because reading through them can be laborsome.

    Often logs can offer misdirection to the actual cause of the panic. I'm more of the firm belief of finding the contributing factors, and trying to isolate the most likely cause based on events that happen prior to it. After all, I wrote a kernel panic FAQ*:

    - * Links to my pages may give me compensation.
  • ~Bee Level 7 (31,425 points)
    Alan --
    My only comment is that when people post logs here on the AD forums,
    other users here who have experience and working knowledge of how to
    start at least basic troubleshooting, can and do help.

    I don't see what the official statement saying that the Apple officials cannot respond
    to every posting has to do with anything.

    Posts asking for help here are never addressed by Apple officials.
    It's all just us other Mac users.
    And most of the time, we're pretty darn effective!
  • Alancito Level 6 (11,095 points)
    Dave — Thanks for your input.
    Dave Sawyer wrote:
    Most people gain little useful information from a crash report and including one by default just make it difficult for people to read about your problem.

    Agreed. But whether the thread is difficult to read depends on how the crash report is posted — which was the point of my post.
    Dave Sawyer wrote:
    If someone asks you to post a crash report...

    I think a potential respondent is more likely to take an interest in the problem if the crash report is already supplied via a link that doesn't make the thread difficult to read.
    Dave Sawyer wrote:
    ...then we just deal with the formatting issue.

    Rather then merely tolerating the "formatting issue" of lengthy inline crash reports, I was hoping readers or Discussions staff could come up with some practical alternatives.

    The following idea of mine is practical for me, but others probably wouldn't want to bother setting up a free, web-based Posterous blog just to post their crash report. ...But once the blog is set up, a PDF of the crash report can easily be created in TextEdit and that PDF emailed as an attachment to — which then automatically creates a blog entry consisting of a slick PDF viewer. So with a hyperlinked thumbnail, I can post future crash reports like this...

    Click below for the crash report:

    ...Perhaps Discussions staff could recommend a way to link to crash reports — for members it makes threads faster to load & easier to read and for Apple it reduces server space & bandwidth usage.

     ~ Alancito
  • ~Bee Level 7 (31,425 points)
    Alan --
    Here's a recent post where the OP (first post)
    uploaded his crash report:

    I wish everyone would do it this way.
    Kinda like what you're recommending.
  • Alancito Level 6 (11,095 points)
    ~Bee: Thanks for that — I tried it out and it looked promising until the site displayed this notice:

    Down for maintenance - 6th Oct 2009 is getting an unprecedented amount of traffic due to a news story in which some leaked Hotmail passwords have been pasted on this site was intended as a tool to aid software developers, not for distributing this sort of material. Filters have been put in place to prevent reoccurrence, but the current traffic level is unsustainable. is just a fun side project for me, and today it's not fun. It will remain offline all day while I make some further modifications

    ...Since many people posting crash reports on these highly trafficked Apple forums may not be +"software developers"+, it's probably inappropriate to recommend using Pastebin's free service.

     ~ Alancito
  • ~Bee Level 7 (31,425 points)
    Well, there's Photobucket and yfrog.
    And several others I've seen used quite a bit . . .
  • Alancito Level 6 (11,095 points)
    ~Bee wrote:
    Well, there's Photobucket and yfrog.
    And several others I've seen used quite a bit . . .

    ~Bee: But can yfrog and photobucket host searchable text/PDF files? ...I could be wrong, but they appear to host images & videos only. (I doubt anyone would want to look at multiple screenshots of a crash report.)

     ~ Alancito
  • Ralph Johns (UK) Level 9 (71,111 points)
    Passing through.

    It has taken me some while to get to grips with the iChat ones.

    This link has an expanded one with Comments

    They refer to Connection problems of one sort or another so what else is loaded into the RAM makes no difference to that so anything below the line "Binary Images for iChat" just take screen space.

    Part of change has come about due to the fact the current Discussions Software allows much longer posts (there used to be a character limit in the previous software) so longer posts can now be made.

    One should also remember that if you post to a thread all those that are Subscribed to it get a complete copy (less pics) as an email alert.
    You can see from th link above that Logs can get very long for iChat.

    10:30 PM Thursday; October 8, 2009

    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
Previous 1 2 Next