On 9 May 2006, at 02:29, Tres Seaver wrote:
>
> Both ESI issues look to be symptoms of the same bug, given the
> backtraces:
>
> - In #975:
> #4 0x080a0263 in ESICustomParser::parse (this=0x85787d8, \
> dataToParse=0x0,lengthOfData=1396) at ESICustomParser.cc:97
>
> - In # 1088:
> #6 0x0809ffef in ESICustomParser::parse(char const*, unsigned,
> bool)\
> (this=0x859f0b8, dataToParse=0xb6f0d064 "on ...") \
> at ESICustomParser.cc:97
>
> Given that the module doesn't even *have* such a line any longer,
> we can
> probably back-burner the bugs (even mark as 'WORKSFORME' or
> something).
> We really need a testcase which includes the triggering data.
>
>
> Tres.
>
Thanks Tres.
In the first instance, I'll leave the bugs open and notify the
reporters that the code has changed, so please could they try to
reproduce with HEAD.
Hopefully they will report unmitigated success and we'll close the
bugs :)
Cheers
Doug
Received on Tue May 09 2006 - 15:33:29 MDT
This archive was generated by hypermail pre-2.1.9 : Thu Jun 01 2006 - 12:00:04 MDT