>>Actually a segfault is likely here, because Apache::Request::Table
>>does not provide a (safe) overload for APR::Table::add().  You cannot
>>currently assign params to any of the APR::Table-derived objects in
>>apreq2, but this isue should be addressed before the next release.
> 
> 
> Having tried Geoffrey's suggestion before this mail arrived I can
> attest to the fact that this does indeed cause segmentation faults for
> the get/set interface and generally bizarre behavior for the tie
> interface.

heh - I hadn't realized that the param() no longer uses apache tables behind
the scenes.  guess I should look at the code more carefully someday.  sorry
for the core dumps :)

--Geoff

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html

Reply via email to