[Webkit-unassigned] [Bug 30827] Off-by-one hard-to-trigger memory corruption in CSSParser (seen only with GCC 4.4)

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=30827





--- Comment #11 from Darin Adler <darin at apple.com>  2009-10-27 13:32:18 PDT ---
(In reply to comment #4)
> (In reply to comment #3)
> > One additional fact I left out: it appears that the discriminating difference
> > to trigger this is GCC 4.4 rather than GCC 4.3.
> 
> That points to either a compiler bug or a side effect of more aggressive
> optimization, then.

(In reply to comment #7)
> It may not be a GCC4.4 optimization issue, but an issue with the lex code
> itself.

Agreed.

What I meant by “side effect of more aggressive optimization” was to raise the
possibility GCC 4.4 might do a correct optimization that GCC 4.3 does not, and
this means that incorrect code produced by lex has a symptom that was latent
before.

If it showed up with GCC 4.3 as well, I would not suspect that, but since it
does not, I do suspect it.

Has anyone reproduced this bug with an unoptimized debug build?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.