[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 12:34:58 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=30827
--- Comment #16 from Darin Adler <darin at apple.com> 2009-10-28 12:34:57 PDT ---
(In reply to comment #15)
> 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.
Seems OK to me, although a bit sloppy.
> 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.
I agree this won’t cause much difficulty debugging the problem.
Typically we hold off on making a change that just makes a bug go away until we
understand why it does. Maybe this is a special case.
--
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