Comments on: iTunes 8.2 Release = Consumer Crash Log Boom to Developers

By: frog

frog — Thu, 04 Jun 2009 01:39:05 +0000

More stable apps can only be a good thing.

By: Josh Hetherington

Josh Hetherington — Wed, 03 Jun 2009 22:46:49 +0000

nice one modmyi.co.uk

By: iDutch

iDutch — Wed, 03 Jun 2009 18:41:12 +0000

Wrong Rene, this isn’t iTunes anymore, it’s iEverything…

By: icebike

icebike — Wed, 03 Jun 2009 18:40:12 +0000

Thanks, Hassan. That is reassuring. I’ve seen other crash dump facilities that exposed all sorts of memory, even from companies (CoughMicrosoftCough) that insist no identifying data was transmitted.

By: Hassan

Hassan — Wed, 03 Jun 2009 18:32:48 +0000

@icebike you will only see a stack trace of the method that blew up. The actual data the the method blew up with is not displayed in the crash report. The developers have no say into the contents of the crash report.

So if your wallet manager crashes the developer should be able to pin point which line of code it crashed at, and the type of error that caused the crash. The data that caused the crash will not be visible in the crash report.

By: icebike

icebike — Wed, 03 Jun 2009 18:25:41 +0000

So can any developers weigh in (anonymously if necessary) as to exactly what (if any) sandboxed data can be obtained in a crash report?

If, say, my wallet manager application crashes, what data does the developer get?