Linked by Amjith Ramanujam on Mon 21st Jul 2008 22:38 UTC, submitted by Moulinneuf
Apple Software engineer Satoshi Nakajima, the lead architect of Microsoft's Windows 95, picked up a Mac for the first time two years ago. He was so impressed, he says he'll never again touch a PC again. Satoshi loves Apple products so much, he started a company in April, Big Canvas, to develop for Apple's iPhone platform full-time. "We have chosen iPhone as the platform to release our first product (for) several reasons," explains his company's website. "We love Apple products... You need love to be creative."
Thread beginning with comment 323986
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Their first product...
by thavith_osn on Tue 22nd Jul 2008 01:09 UTC in reply to "RE[3]: Their first product..."
thavith_osn
Member since:
2005-07-11

True, but Apple's kernel doesnt' produce those gloriously useless and cryptic registry addresses that reveal nothing about what the hell just puked.

I write file system drivers for Windows. When the machine blue screens (which is very common sadly (due to my great programming skills - lol)) it gives me a detailed report of what just happened. You just have to know how to read it. It has saved me hours of debugging.

The Mac's SOD is nicer than the BSOD, but no more enlightening. It doesn't tell you why your machine just "puked", only that it did and how to restart it. There is a dump that you can look at however (just like Win and Lin), but again, you have to know how to read it...

I've not seen the Linux SOD for a while (I hardly run Linux sadly), so can't comment on the amount of detail there...

Reply Parent Score: 7

RE[5]: Their first product...
by tyrione on Tue 22nd Jul 2008 01:34 in reply to "RE[4]: Their first product..."
tyrione Member since:
2005-11-21

True, but Apple's kernel doesnt' produce those gloriously useless and cryptic registry addresses that reveal nothing about what the hell just puked.

I write file system drivers for Windows. When the machine blue screens (which is very common sadly (due to my great programming skills - lol)) it gives me a detailed report of what just happened. You just have to know how to read it. It has saved me hours of debugging.

The Mac's SOD is nicer than the BSOD, but no more enlightening. It doesn't tell you why your machine just "puked", only that it did and how to restart it. There is a dump that you can look at however (just like Win and Lin), but again, you have to know how to read it...

I've not seen the Linux SOD for a while (I hardly run Linux sadly), so can't comment on the amount of detail there...


In writing filesystems you also have access to the debug code, tracers and more to help give feedback, besides the reference manual to describe each error in detail.

The average mortal doesn't have access to this and to them it's garbage. The more revealing and discernible the error messages are inherently speaks volumes to filesystem developers who take that into consideration.

Reply Parent Score: 3

Ford Prefect Member since:
2006-01-16

here is a kernel oops for you:

http://fopref.meinungsverstaerker.de/div/oops.png

(this one didn't lead to a kernel crash)


you see the information there ... complete backtrace.

Reply Parent Score: 2

RE[6]: Their first product...
by hobgoblin on Tue 22nd Jul 2008 08:50 in reply to "RE[5]: Their first product..."
hobgoblin Member since:
2005-07-06

and even for someone that dont read hex daily, thats potentially informative.

reiserfs that was acting up?

Reply Parent Score: 2

RE[5]: Their first product...
by merlimat on Tue 22nd Jul 2008 11:31 in reply to "RE[4]: Their first product..."
merlimat Member since:
2008-07-22

In Mac OS X after a reboot forced by a kernel panic, you will find the stack trace dumped in a file.

Additionally, in MacOS X you can put the kernel in debug mode. This means that, in case of a kernel panic, you can have the dump of the entire kernel memory sent to another machine and analyze it with gdb.

Reply Parent Score: 1

RE[6]: Their first product...
by apoclypse on Tue 22nd Jul 2008 13:42 in reply to "RE[5]: Their first product..."
apoclypse Member since:
2007-02-17

You also get a dialogue when you login after a kernel panic asking you if you want to report the issue. This dialogue holds the details about the kernel panic and usually gives you the relevant info pertaining to the crash. I used it to find out that 10.5.2 was having issues with Firewire interfaces, though that was obvious since I would get a kernel panic every time I connected my Audio interface to my MBP.

Reply Parent Score: 2