In article <4803434c$0$889$ba4acef3@news.orange.fr>,
John Stolz <china_rider.RemoveThis@wanadoo.fr> wrote:
> Doc O'Leary wrote:
> > In article <47fef3a7$0$883$ba4acef3@news.orange.fr>,
> > John Stolz <china_rider.RemoveThis@wanadoo.fr> wrote:
> >
> >> But the date is wrong, the Mac OS X version is wrong and the version of
> >> RapidWeaver is wrong. I presume this relates to an earlier crash.
> >> How do i get a report on the current crash?
> >
> > Look further along in the file. New crash reports get appended.
> >
> There is only one crash reported in the crash reporter and only one file
> associated with this program (rapidweaver.crash.log)
Then you may be looking at the wrong crash log. For example, I've had
processes that go *really* bad such that their crash logs are written to
/Library/Logs/CrashReporter with name like "???.crash.log" and "Exited
process.crash.log" Since you don't give any details about the crash
itself, all I can say is perhaps you should search for files that were
modified around the time of the crash.
--
My personal UDP list: 127.0.0.1, 4ax.com, buzzardnews.com, googlegroups.com,
heapnode.com, localhost, ntli.net, teranews.com, vif.com, x-privat.org
>> Stay informed about: How do i get a current crash report?