[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 #12 from Craig Schlenter <craig.schlenter at gmail.com>  2009-10-28 08:58:55 PDT ---
Joel's backtrace appears to have come from a debug build:

>From valgrind-lapack.txt from
http://code.google.com/p/chromium/issues/detail?id=23362#c41

tools/valgrind/valgrind.sh out/Debug/chrome --user-data-dir=/tmp/chrome
http://www.cs.colorado.edu/~jessup/lapack/

Darin: would you consider a patch that cranks up the buffer size to work around
this temporarily until we can make more sense of this?

I unfortunately can't reproduce this on my machine so debugging it is
problematic :(

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