I think I have it working now (with the mod_include
changes that I just committed). Mod_include test #31
in httpd-test is failing, but I think it's a config
problem.
We probably need some more test cases in httpd-test
to validate all the boundary conditions that can occur
in mod_include when SSI directives span multiple buckets
or even multiple brigades.
--Brian
Ian Holsman wrote:
> Cliff Woolley wrote:
>
>> On 24 Feb 2002 [EMAIL PROTECTED] wrote:
>>
>>
>>> HTTPD-test is failing.
>>> but it was failing on 2.0.32 version of mod-include as well
>>>
>>
>> Really?? What's the verbose output? It worked fine for me when I
>> tested
>> 2.0.32... I'll try it again with HEAD tomorrow.
>>
>> --Cliff
>>
>>
> 2.0.32 is clean
> 2.0.32 + CVS-HEAD of mod-include
>
>
> # testing : GET /modules/include/exec/off/cmd.shtml
> # expected: '[an error occurred while processing this directive]'
> # received: ''
> not ok 8
>
> # testing : GET /modules/include/exec/off/cgi.shtml
> # expected: '[an error occurred while processing this directive]'
> # received: ''
> not ok 30
>
> and we get a core-dump
> in handle_exec/mod_cgi
>
> it looks like the ctx has some bad data
> (gdb) print *ctx
> $6 = {state = PARSED, flags = 11, if_nesting_level = 0, parse_pos = 3,
> bytes_parsed = 39, status = 0, output_now = 0, head_start_bucket = 0x0,
> head_start_index = 135541272, tag_start_bucket = 0x0,
> tag_start_index = 135541272, tail_start_bucket = 0x5, tail_start_index
> = 135541272,
> combined_tag = 0x24 <Address 0x24 out of bounds>, curr_tag_pos =
> 0xbfffe2a0 "exec", directive_length = 3221217957, tag_length = 4,
> error_str = 0x1f <Address 0x1f out of bounds>, error_str_override =
> 0x80944a0 "[an error occurred while processing this directive]",
> time_str = 0x0, time_str_override = 0x8093a95 "%A, %d-%b-%Y %H:%M:%S
> %Z", pool = 0x0, ssi_tag_brigade = 0x8143730, start_seq_pat = 0x8143ba8,
> start_seq = 0x8141b0c "", start_seq_len = 134822578, end_seq = 0x5
> <Address 0x5 out of bounds>, re_string = 0x8093aae "-->", re_result =
> 0x0}
> (gdb)
>
>