Saxon » SaxonC

64-bit machine and php 5.4

Hi, I am still trying to reproduce the seg error under centos 64-bit. Do you have any log file generated from the error either in the php log folder on where the libsaxon.so lives?

The following page might help: http://forums.cpanel.net/f5/php-segfault-problem-205902.html#post845372

Hi, I've had to format the server, so that I do not send you the log files.

Did you install saxon/c successfully on centos 7 64-bit machine?

Hi, so far I did manage to compile and install saxon\c with the PHP extension on a vm centos 64-bit.

The bit that was tricky was the locating of the jni.h file. I had to install java-jdk then add the classpath to the file. Without this jni step the compilation fails with a lot of errors.

I am now getting libsaxon.so not found when I try to run with a PHP script example which uses the saxon\c API. I will investigate this today.

Update on progress:

I thought I would share my experience on installing Saxon/C on centos 7 (64-bt machine) in hope it might help you to solve the set error.

Firstly, I had to copy the rt and the saxon-data directory along with the libsaxon.so library to the directory /usr/lib64 instead of the directory /usr/lib. I have fixed this instruction on the website.

Secondly, you should try to compile and run the C++ API. This can be done as follows:

g++ -g -o SaxonProcessor SaxonProcessor.cpp -ldl -lsaxon -lstdc++ -DCPP_ONLY
./SaxonProcessor

AS mentioned in comment 6: The compilation depends on Java headers otherwise you get an error with the jni.h not found:

CPLUS_INCLUDE_PATH=/usr/lib/rt/amd64:$JAVA_HOME/include/linux:$JAVA_HOME/include
export CPLUS_INCLUDE_PATH

Thirdly, I had to do the following to solve the error 'libjvm.so cannot open shared object file':

ln -s  /usr/lib64/rt/lib/amd64/jetjvm/libjvm.so /lib/libjvm.so

At this point the C++ program should run.

Hi,

I reported the JET log file to Excelsior. Here is their response:

This is a crash inside GlibC library which may be caused by plenty of
various reasons (even bugs in Glibc itself).

Try to update libc library if it is
possible and check if the crash persists.

Hi,

Following some correspondence with Excelsior Jet, we managed to get to the bottom of the segmentation fault, which was reported.

We think that the problem is indeed a bug in the test program of the Saxon/C code. It assumes that the test files are in the location: /var/www/trax

Summary from Jet:

We found that the crash happens because of JNI-misuse in the code you've provided.
 
So, if we don't have /var/www/trax directory in the system then the following happens:
 
1) C++ method XsltProcessor::xsltSaveResultToFile is called from main();
2) This method then calls XsltProcessor::xsltApplyStylesheet() which calls Java-method XsltProcessorForCpp.xsltApplyStylesheet() via JNI;
3) XsltProcessorForCpp.xsltApplyStylesheet() throws an exception which is not handled in C++ code and NULL is returned by this JNI call;
4) As the result XsltProcessor::xsltApplyStylesheet() also returns NULL;
5) Then XsltProcessor::xsltSaveResultToFile() takes the returned value (NULL) and calls fputs() C-function with this value as a parameter;
6) fputs() calls strlen() using the provided parameter (NULL) causing segmentation fault;
7) JET runtime handles this segmentation fault creating the crash log.

The C++ and PHP interfaces should work fine.

A fix will be applied in the next release for the test program. As a workaround you should be able to to change the main method in SaxonProcessor.cpp to run the tests files from a location of your choice, by setting the current working directory using the method setcwd().

Hi Eirik,

Thanks for providing such a detailed step-by-step setup guide on Centos 7. I will look into this shortly.

Thank you for looking into this matter.

Do you have any new estimate on the next release of Saxon/C?

Sorry no. Not setting any firm deadline yet. But we are getting close. Currently in testing phase and some refining of the API.