It’d be more helpful to know what the NSException was. Without that information, it’s nearly impossible to figure out what’s going on from the stack trace alone. Debug symbols would help too, but if you’re using Java Packager that won’t be an option (sounds like an RFE waiting to happen..). Which version of the packager are you using? If you’re not already, please try the packager in 8u40, it’s much more mature than earlier releases.
-DrD- > On Mar 10, 2015, at 9:01 AM, Emmanuel Puybaret <puyba...@eteks.com> wrote: > > Hi, > > Thanks for your suggestion. Unfortunately, I don't believe it's a mix between > 32 and 64 bit libraries. > In the sandboxed version I distribute, binaries are built with an Ant script > which removes the 32 bit version of libraries with lipo. > > Doesn't the stack trace give some hints to some of you? > I think that people who have problems with this sandboxed application don't > use a system issued from a clean install. > Some others reported also that the program hangs when they try to use a > FileDialog. > Could there be some old incompatible libraries still there in the system that > would provoke this kind of error? > > Best regards, > -- > Emmanuel PUYBARET > Sweet Home 3D developer > Email : puyba...@eteks.com > Web : http://www.eteks.com > http://www.sweethome3d.com > >> Le 9 mars 2015 à 23:47, Peter J Slack <psl...@wavedna.com> a écrit : >> >> looking at your build.xml on CVS browser . . possible you are using 32 bit >> JOGL libraries . .you will want to update all your native binary libraries >> for OSX to 64 bit .. that's just what jumped out I haven't looked at the >> whole file .. >> >> 213 <target name="java3dAllSystemsLibrary" depends="jogl-java3d" >> 214 description="Builds applet Java 3D library suitable for all >> systems in deploy/lib subdirectory"> >> 215 <mkdir dir="deploy/lib"/> >> 216 <!-- Create java3d.jar containing Java 3D DLLs and jars for >> Windows, Linux and Mac OS X >> 217 (this library is used for Java versions older than Java SE 6 >> update 10) --> >> 218 <jar destfile="deploy/lib/java3d.jar" >> manifest="build/META-INF/MANIFEST.MF"> >> 219 <fileset dir="lib"> >> 220 <include name="j3dcore.jar"/> >> 221 <include name="j3dutils.jar"/> >> 222 <include name="vecmath.jar"/> >> 223 </fileset> >> 224 <fileset dir="lib"> >> 225 <include name="windows/**/*.dll"/> >> 226 <include name="linux/**/*.so"/> >> 227 <include name="macosx/**/*.jnilib"/> >> 228 <include name="macosx/**/*.jar"/> >> 229 <exclude name="macosx/*/jogl-all.jar"/> >> 230 </fileset> >> 231 <fileset dir="build"> >> 232 <include name="macosx/java3d-1.6/jogl-java3d.jar"/> >> 233 </fileset> >> 234 </jar> >> 235 </target> >> >> >> >> On Mon, Mar 9, 2015 at 1:12 PM, Emmanuel Puybaret <puyba...@eteks.com> wrote: >>> Sorry for the late answer but I had some new information to share about >>> this issue. >>> I asked the user who got a JRELoadError to try to launch the program on a >>> new user account but this didn't help. >>> He also reported the following stack trace which make him wonder if there >>> could be an incompatible DLL somewhere: >>> >>> 2015-02-11 18:01:08.693 SweetHome3D[1073:707] Could not get function >>> pointer for JLI_Launch.: ( >>> 0 CoreFoundation 0x00007fff8cf2fb06 >>> __exceptionPreprocess + 198 >>> 1 libobjc.A.dylib 0x00007fff928f13f0 >>> objc_exception_throw + 43 >>> 2 CoreFoundation 0x00007fff8cf2f8dc >>> +[NSException raise:format:] + 204 >>> 3 SweetHome3D 0x00000001000017fe launch + >>> 499 >>> 4 SweetHome3D 0x0000000100001578 main + 76 >>> 5 SweetHome3D 0x0000000100001524 start + 52 >>> 6 ??? 0x0000000000000001 0x0 + 1 >>> >>> Hope this will help, >>> -- >>> Emmanuel PUYBARET >>> Sweet Home 3D developer >>> Email : puyba...@eteks.com >>> Web : http://www.eteks.com >>> http://www.sweethome3d.com >>
