Both operating systems have this functionality to some level. There
are security concerns that the vendors take seriously, that limit the
usability of the automated crash reports. It is significantly better
to use feedback channels with recipes (directions) for causing a
crash. Especially if
You know what I think would be really neat? If Apple was to do what
GwMicro did with Window-Eyes; make the operating system self-healing.
This concept for GwMicro involved collecting crash logs from people's
machines when they rebooted; the Window-Eyes software phoned home and sent
the crash
Greetings,
I intermittently experience restarts of voiceOver. With the exception of doing
a google search in Safari I do not have a reproducible test case that I could
present to Apple. My question is whether there is a log written when an app
crashes? If so is there a system setting that
If my memory is correct, there is a logs directory in your library I
believe I have seen crash information for VO among the logs there, and
the console program can read these log files.
Jn
On 14/10/2010, GEOFF WAALER geoff.waa...@gmail.com wrote:
Greetings,
I intermittently experience
Hello Geoff,
To find Crash Logs, go to your Home folder, then Logs, then Crash Logs, and
that's where they'll be. Except that VO stopping speaking doesn't generate a
crash log. Strictly speaking, it isn't a crash since the VoiceOver cursor is
still visible on the screen (or so I'm told).
Every time I attach those though mail won't send the message as it has problems
attaching that crash report. I've had this problem and apple cannot open my
crash reports I send them.
S
On Oct 14, 2010, at 8:35 AM, Jonathan Cohn wrote:
If my memory is correct, there is a logs directory in your
