Industry


Ads by TechWords

See your link here


Frank Hayes's picture
Frank Hayes

Frankly Blogging

Word 2007 crashes: A feature, not a bug?

Let me see if I understand Microsoft's philosophy about malformed documents that crash Word 2007. In the words of an unnamed Microsoft spokesmushroom: "In fact, the behavior observed in Microsoft Word 2007 in this instance is a by-design behavior that improves security and stability by exiting Microsoft Word when it has run out of options to try and reliably display a malformed Word document....The sample code in [Aharoni's] postings cause Microsoft Word to crash, and users can restart the application to resume normal operations."

So can we expect to see that approach in other products that use Windows Embedded?

Like maybe...a TV that, when the cable service goes pixellated, shorts out all the circuitry in your house? ("Users can reset circuit breakers to resume normal operations.")

A car CD player that, when it's fed a scratched disc, disconnects the steering and brakes and disengages the clutch? ("Users who survive can restart the car to resume normal operations.")

A cell phone that, when the conversation gets too banal, shuts down your relationship? Oh, wait -- that's been done.

David LeBlanc -- quoted in the news story as a Microsoft secure-code guru -- says "it is better to crash, at least with client apps, than it is to be running the bad guy's shell code." Hooey.  This is no either/or situation. For years, Word has been able to announce that a document is malformed and can't be loaded. (Which Word regularly does to me with file formats it doesn't recognize, so I know that notion isn't new to Microsoft's programmers.)

If your application code is in control, it can gracefully reject bad input.

If your app code ISN'T in control, you crash. You're already owned.

This suicide-before-capture approach isn't "by-design" behavior. It's lack-of-design behavior.

And a "code guru" of any kind who thinks that's not a security and stability problem that needs fixing doesn't belong in this business.

What People Are Saying

I heard about not bad

I heard about not bad application-microsoft word text recovery, can work with .doc, .docx, .dot and .dotx files and with any version of Microsoft Word text editor, can recover only plain text, it means, that text formatting, graphics and all other elements will be lost, can recover your data from corrupted *.doc files, located on corrupted media: floppy and CD disks, flash and zip drives, etc.,This tool can be used by anyone, your level of computer skills does not matter.

... so tell me people, why

... so tell me people, why does Word 2007 crash when you try to send a document as email?

I've long suspected that the

I've long suspected that the BSOD was just a Windows security feature also.

Zigging where Anonymoose

Zigging where Anonymoose zags -- Frank, "spokesmushroom?" Funnier every time I see it. Though I hope you know this will go down on your permanent WaggEd record...

I think Frank Hayes is

I think Frank Hayes is exaggerating the severity of a software application crash. His analogies would be more equivalent to Microsoft Word 2007 causing at least a system reboot, and at most the loss of all data on the hard drive to which Microsoft Word 2007 was installed.

Incidentally, I think Frank Hayes is trying too hard to be funny.

It is simple, we all must

It is simple, we all must publicize the problem and lobby people not to buy the product. Microsoft has for years used their customers as guinea pigs with Beta and unfinished code. Now is the time for Microsoft to be exposed for what they are.
Word 2007 is unuseable and should not be bought until they fix it, period.

Any one of you would be a

Any one of you would be a lying to suggest that they have written perfect code, or that even after fixing bugs, there are no more bugs left. This 'feature' that MS is touting around is, in fact, the exceptional case where a bug was unfortunately not found before release.

Nobody here is surprised that serious bugs were found in Microsoft software. The general air of incredulous amusement is found in Microsoft claiming that the equivalent of a segmentation fault is the designed response to a malformed input.

As every student in every reputable university software engineering program knows, the proper response to a malformed input is to catch the exception and cleanly report it.

I'll happily state for the record that any crash from any program I specified or coded over the past 30 years is a bug. I'll fix it or your money back.

If only Microsoft were as honest.

To jf: Your 'position' is

To jf: Your 'position' is entirely moronic. If some of my coders ever uttered such a thing I can't say I would fire them instantly (I'm not american and therefore the 'you're fired' happรƒยฌness doesn't apply as much) but that poor schmuck would be detached from coding with NO explanation (what's the use) and become the guy to drill holes in the wall or any other tasks suiting his brainpower. No, mate, crashing is NEVER an option. You super-idiot. Tell that to the makers of medical software, tell that to the JPL. Tell that to the ESA engineers. Tell that to the coders of ABS/Airbag deplyment software. If you don't want to do a perfect work you don't belong in this business. I'd suggest you apply for a coder position at Microsoft.

Actually, other programs

Actually, other programs often are better at parsing MS Office files:
I work as a teacher and students often ask for help because they have an important doc they can't open (and no backup, or the backup is at home and they need the file now): in many cases, trying to open the file (doc, ppt) in Staroffice or openoffice at least saves part of the contents of the file while word/ppt crashes right away

Having been a programmer for

Having been a programmer for over 25 years, I have always taken a program fault as a personal insult. I consider that I do not want code that I have written to fail, and if an application fails because of bad input, that represents either incompetence or misconduct amounting to negligence. Granted, there may be some things you can't recover from, e.g. if the database is corrupted the database management system may crash and not allow you to recover, but for a word processor, this sort of behavior (and attitude) is inexcusable. It's this sort of arrogant pedantry which makes me glad I use Word Perfect and (when unavoidable) Open Office and do not use Microsoft Word.