Our use of Adobe Live Cycle ends up using the CORBA connected XML Forms native executable.
We are getting a segmentation fault from this XML Forms native executable when it has been called, causing all of our xml form submissions to fail.
Is there any way I can get a version of XMLForms that has debug enabled?
Or is there something other than the core dump that we can send to Adobe to help us with this issue? We have a ticket open with them, but I figured I'd open this up to the community as well to see if anyone has experienced this before.
So that I can track down the root cause of a segmentation fault?
I've seen this post: http://blogs.adobe.com/livecycle/2010/12/native-c-components-of-livecycle.html
And this post: http://blogs.adobe.com/livecycle/2011/11/debugging-form-rendering-issues-related-to-xmlforms-native-...
And this post: http://blogs.adobe.com/dmcmahon/2012/07/18/livecycle-es2-xmlform-exe-terminated-abnormally-with-erro...
The most useful information i pulled out of these steps are that the XMLForm.exe script can be edited. So I can add some debugging to get the guilty party of what .so caused this seg fault.
I was hoping for a magic LD_LIBRARY_PATH setting that might correct this problem by avoiding a bad lib.
My next idea was to add valgrind to the XMLForm.exe script and see what extra information that will give me.
any other ideas? any help would be appreciated thanks!!!
