[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
Wed Oct 28 11:27:38 PDT 2009


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





--- Comment #15 from Craig Schlenter <craig.schlenter at gmail.com>  2009-10-28 11:27:38 PDT ---
(In reply to comment #13)
> If our primary goal is to diagnose and fully fix the problem, it’s possible
> that applying a patch that makes its symptoms go away for reasons we don’t
> fully understand may make our task more difficult rather than easier. Perhaps
> you have another goal?

My goal was to stop possible crashes in the field without requiring package
builders using gcc 4.4 to carry extra patches until the problem is properly
resolved. Part of the rationale for suggesting this was that it looks like the
problem might take a while to solve and I was anticipating that when debugging
the problem it would be easy to revert the patch locally if desired.

But if you feel that approach is undesirable, it's easy enough for the
packagers to include a local patch for now...

-- 
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