[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
bugzilla-daemon at webkit.org
Tue Oct 27 11:39:03 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=30827
Darin Adler <darin at apple.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Off-by-one hard-to-trigger |Off-by-one hard-to-trigger
|memory corruption in |memory corruption in
|CSSParser |CSSParser (seen only with
| |GCC 4.4)
--- Comment #4 from Darin Adler <darin at apple.com> 2009-10-27 11:39:03 PDT ---
(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. It doesn't happen to
> Google-based Chrome developers who are using GCC 4.3 (and likely also OS X
> WebKit devs). It does happen to people building on both Fedora and Ubuntu with
> GCC 4.4.
That points to either a compiler bug or a side effect of more aggressive
optimization, then.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list