Pretty hard. C is a minefield of undefined behavior. Integer overflow is considered undefined behavior. Which means its perfectly valid to call abort(), wipe your hard drive, then light your system on fire. Or, have the number quietly wrap around.

Oh, and its perfectly fine for me to change the behavior from one to the other, or even have a lookup table of random responses to undefined behavior. Because, like, you're not following the standard. And its so easy.

> C is a minefield of undefined behavior. Integer overflow is considered undefined behavior.

Only for signed integers. Unsigned integers are defined to wrap around.

Yea, I remember the joke about gcc #pragma once causing something like rogue to run.

For what it's worth, I agree. Every time I hear about problems that arise from programming in C, with its undefined behaviour etc., I think to myself, there must be a better way to do it. But I don't know of any way that wouldn't involve scrapping 90%+ of software we use every day.

Precisely.

It also indicates that Adobe don't run their code through valgrind, which would have picked this problem up.

Considering that flash is (a) security critical and (b) often full of security bugs, you'd think they might run valgrind over it once in a while.

Entirely Adobe's fault this one.

BTW with Firefox 4 the need for flash has virtually gone. All the popular video sites can play most of their videos using the native video support in the browser.

I was under the impression that Valgrind didn't play nice with virtual machines.

Generally no, out of the box it doesn't, things like JITs and GCs can confuse it, however it's got a bunch of flags and config options and what not to allow you to use it.