Thomas Dickey dixit: > The one I have in mind was this: > > * replace fixed-buffer Style_className[] with a dynamically-allocated buffer, > needed for large pages which lack correctly-nested tags, e.g., > http://www.aspas-nature.org/petitions/petition2.html > (reported by Frederic L W Meunier) -TD > > The problem was that a fixed-buffer (under src) was used for storing a stack > of > names. When it ran past the end of the buffer, adjacent data was overwritten, > causing a secondary problem down in the WWW logic, and finally a core dump.
Hm, strlcpy and truncation detection, or so? What about having a buffer which grows as needed, but there is always exactly one allocated? > Narrowing the problem down to see where the first problem can be observed is > the first step. The cause may be far removed from the symptom - which is why > it's nice to have a case that can be repeated (in debugging, I repeat those > cases many times ;-) Sure, but I can't reproduce it. The last one happened when going from slashdot (light layout) to OSnews (in a slashbox), but there were at several other pages too, and never twice at the same, not even if reproducing the "surfing" behaviour. bye, //mirabile _______________________________________________ Lynx-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lynx-dev
