Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I never get crash logs when an application crashes, and the reason is that CrashReporter itself crashes:

4/20/12 10:11:25 AM[104]
([133]) Job appears to have crashed: Trace/BPT trap

A google search shows that I'm not the only person to experience this. But I haven't found a definitive cure. A popular google hit suggests moving the LaunchAgents .plist file from the System LaunchAgents to the User LaunchAgents, but that made no difference for me. I'm wondering if anyone has actually solved this.

(This is on Snow Leopard. I have a Lion installation and another Snow Leopard computer; the problem doesn't occur there. It's just this one volume.)

share|improve this question
Are you looking to learn how to narrow down a crash report or just move on? – bmike Jul 2 '12 at 15:34

try these two things:

  1. boot to safe mode, and then reboot. (hold Shift at system chime)
  2. boot to single user mode, delete /Systems/Library/Caches & subdirectories

fixed lots of crash reporter errors on my machine.

share|improve this answer

If you can reproduce this on a clean installation on that machine, it might be interesting to track down why and how the OS has become corrupted. It's not a tidy answer, but even for someone that can debug things - without the source code to the program this may be chasing a needle in a haystack to know why one of your computers isn't happy when it's crashing.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.