Aaron Straup Cope <asc@[...].net>  writes:

>  Hi all,
> 
>  I am trying to determine where a problem that is causing a program, that
>  makes extensive use of XML::LibXSLT functions, to dump core. 

Search the archive for most recent threads on this topic. I posted a
patch for LibXSLT there which seemed to fix the problem.

>  libxml 2.6.4      (FBSD ports)

AFAIK, latest libxml2 release is known to have bugs in XInclude code
(causing 02parse.t to fail). CVS libxml2 is claimed to fix the problem
(and LibXML's self-tests pass on my Linux box), but I'm still
suspicious because valgrind still reveals some illegal reads. I didn't
manage to investigate that further, being too busy last few days.

>  Is this a known failure? If it is not could someone suggest the next
>  step for tracking down the problem? If it really is just a question of
>  ripping out all the functions and adding them one at a time, I will do
>  that but it's not my first choice.

Try the combination of latest CVS libxml2, CVS LibXML, CVS LibXSLT, my
patch you'll easily find in the archives. There shouldn't be any
self-test errors with this combinations, and there is a chance that
your extension functions problems will be fixed also. If there are
still self-test failures, and you wanna help, locate the problematic
test (use TEST_VERBOSE=1), use valgrind or debugger on 'perl -Mblib
t/XYtest.t' to find out what's happening, and try if the problem can
be reproduced with just xmllint or libxslt. If yes, send a bugreport
to libxml2 mail-list. If no, send it here.

-- Petr
_______________________________________________
Perl-XML mailing list
Perl-XML@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs