Re: [Fink-users] Octave (developer srcs) builds, but results in bus-error
On Nov 23, 2009, at 4:39 PM, Martin Costabel wrote: Ben Abbott wrote: On Nov 22, 2009, at 10:09 AM, Martin Costabel wrote: [] Did the CrashReporter write something in ~/Library/Logs? [] The file below is from ~/Library/Logs/DiagnosticReports. I don't really know what's going on; I can only speculate. What looks suspicious to me is the following: There are two copies of libstdc++ loaded 0x2bf7000 - 0x2c88fe7 +libstdc++.6.dylib /sw/lib/gcc4.4/lib/libstdc++.6.dylib 0x98a75000 - 0x98adffe7 libstdc++.6.dylib /usr/lib/libstdc++.6.dylib The crash happens inside Apple's libstdc++, and this seems to be pulled in from liboctinterp-3.3.50+.dylib. Did you compile parts of that dylib with Fink's c++-4.4 and parts with Apple's c++-4.2? Maybe this leads to the crash. -- Martin I have a rather poor understanding for how libtool works. It does appear that either I've linked to gcc 4.4 and gcc 4.2's dylibs, or that the 4.2 version is erroneously being loaded at run time. Using otool to look at the binary ... $ otool -L src/.libs/octave src/.libs/octave: /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0) /sw/lib/gcc4.4/lib/libgfortran.3.dylib (compatibility version 4.0.0, current version 4.0.0) /sw/lib/octave-3.3.50+/liboctinterp-3.3.50+.dylib (compatibility version 0.0.0, current version 0.0.0) /sw/lib/octave-3.3.50+/liboctave-3.3.50+.dylib (compatibility version 0.0.0, current version 0.0.0) /sw/lib/octave-3.3.50+/libcruft-3.3.50+.dylib (compatibility version 0.0.0, current version 0.0.0) /sw/lib/libpcre.0.dylib (compatibility version 1.0.0, current version 1.1.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.0.0) /sw/lib/libGraphicsMagick.3.dylib (compatibility version 6.0.0, current version 6.0.0) /sw/lib/libfftw3.3.dylib (compatibility version 6.0.0, current version 6.4.0) /sw/lib/libfftw3f.3.dylib (compatibility version 6.0.0, current version 6.4.0) /sw/lib/fltk-aqua/lib/libfltk_gl.1.1.dylib (compatibility version 1.1.0, current version 1.1.4) /System/Library/Frameworks/AGL.framework/Versions/A/AGL (compatibility version 1.0.0, current version 1.0.0) /sw/lib/fltk-aqua/lib/libfltk.1.1.dylib (compatibility version 1.1.0, current version 1.1.4) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 152.0.0) /sw/lib/freetype219/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.19.0) /sw/lib/libhdf5.0.dylib (compatibility version 1.0.0, current version 1.0.0) /sw/lib/libsz.2.dylib (compatibility version 3.0.0, current version 3.0.0) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) /usr/X11/lib/libfontconfig.1.dylib (compatibility version 5.0.0, current version 5.0.0) /usr/X11/lib/libX11.6.dylib (compatibility version 9.0.0, current version 9.0.0) /sw/lib/libreadline.5.dylib (compatibility version 5.0.0, current version 5.0.0) /sw/lib/ncurses/libncurses.5.dylib (compatibility version 5.0.0, current version 5.0.0) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate (compatibility version 1.0.0, current version 4.0.0) /sw/lib/gcc4.4/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) It appears that the proper gcc 4.4 dylibs are listed. Looking at the interpreter's library ... $ otool -L src/.libs/liboctinterp.dylib src/.libs/liboctinterp.dylib: /sw/lib/octave-3.3.50+/liboctinterp-3.3.50+.dylib (compatibility version 0.0.0, current version 0.0.0) /sw/lib/octave-3.3.50+/liboctave-3.3.50+.dylib (compatibility version 0.0.0, current version 0.0.0) /sw/lib/octave-3.3.50+/libcruft-3.3.50+.dylib (compatibility version 0.0.0, current version 0.0.0) /sw/lib/libpcre.0.dylib (compatibility version 1.0.0, current version 1.1.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.0.0) /sw/lib/gcc4.4/lib/libgfortran.3.dylib (compatibility version 4.0.0, current version 4.0.0) /sw/lib/libGraphicsMagick.3.dylib (compatibility version 6.0.0, current version 6.0.0) /sw/lib/fltk-aqua/lib/libfltk_gl.1.1.dylib (compatibility version 1.1.0, current version 1.1.4) /sw/lib/fltk-aqua/lib/libfltk.1.1.dylib (compatibility version 1.1.0, current version 1.1.4) /sw/lib/libfftw3.3.dylib (compatibility version 6.0.0, current version 6.4.0) /sw/lib/libfftw3f.3.dylib (compatibility version 6.0.0, current version 6.4.0) /sw/lib/libhdf5.0.dylib (compatibility version 1.0.0, current version 1.0.0) /sw/lib/libsz.2.dylib (compatibility version 3.0.0, current version 3.0.0) /usr/lib/libz.1.dylib (compatibility version
Re: [Fink-users] Octave (developer srcs) builds, but results in bus-error
Ben Abbott wrote: [] Is it possible that the wrong dylib is being loaded at run time? Is there a way to (safely) test the idea? The other libstdc++ is loaded because it is pulled in by some of the dylibs liboctinterp-3.3.50+.dylib links to, for example /sw/lib/fltk-aqua/lib/libfltk_gl.1.1.dylib. You can see in which order the dylibs are loaded by running octave as env DYLD_PRINT_LIBRARIES=1 octave Another env variables interesting in this context is DYLD_PRINT_BINDINGS (but its output is enormous). Note that I am not sure that this is really the cause of the crash. It would be interesting to see if others know about crashes that appear when dylibs compiled with different versions of g++ are linked together. -- Martin -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Octave (developer srcs) builds, but results in bus-error
On Nov 24, 2009, at 8:23 PM, Martin Costabel wrote: Ben Abbott wrote: [] Is it possible that the wrong dylib is being loaded at run time? Is there a way to (safely) test the idea? The other libstdc++ is loaded because it is pulled in by some of the dylibs liboctinterp-3.3.50+.dylib links to, for example /sw/lib/fltk-aqua/lib/libfltk_gl.1.1.dylib. You can see in which order the dylibs are loaded by running octave as env DYLD_PRINT_LIBRARIES=1 octave Another env variables interesting in this context is DYLD_PRINT_BINDINGS (but its output is enormous). Note that I am not sure that this is really the cause of the crash. It would be interesting to see if others know about crashes that appear when dylibs compiled with different versions of g++ are linked together. -- Martin Looking at the libstcd++.6.dylib's for gcc4.2 and gcc4.4, it appears (to me) that compatibility problems are to be expected. $ otool -L /sw/lib/gcc4.4/lib/libstdc++.6.dylib /sw/lib/gcc4.4/lib/libstdc++.6.dylib: /sw/lib/gcc4.4/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.13.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 124.1.1) /sw/lib/gcc4.4/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) $ otool -L /usr/lib/libstdc++.6.dylib /usr/lib/libstdc++.6.dylib: /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 123.0.0) Is there a simple way to build fltk using gcc 4.4? Ben -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Octave (developer srcs) builds, but results in bus-error
Ben Abbott wrote: On Nov 22, 2009, at 10:09 AM, Martin Costabel wrote: [] Did the CrashReporter write something in ~/Library/Logs? [] The file below is from ~/Library/Logs/DiagnosticReports. I don't really know what's going on; I can only speculate. What looks suspicious to me is the following: There are two copies of libstdc++ loaded 0x2bf7000 - 0x2c88fe7 +libstdc++.6.dylib /sw/lib/gcc4.4/lib/libstdc++.6.dylib 0x98a75000 - 0x98adffe7 libstdc++.6.dylib /usr/lib/libstdc++.6.dylib The crash happens inside Apple's libstdc++, and this seems to be pulled in from liboctinterp-3.3.50+.dylib. Did you compile parts of that dylib with Fink's c++-4.4 and parts with Apple's c++-4.2? Maybe this leads to the crash. -- Martin -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Octave (developer srcs) builds, but results in bus-error
Ben Abbott wrote: On Nov 21, 2009, at 4:25 PM, Martin Costabel wrote: Ben Abbott wrote: [] Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x 0x02c0702f in std::locale::operator= () (gdb) Maybe a backtrace bt would give some more insight. -- Martin ... or maybe not :-( (gdb) bt No stack. Did the CrashReporter write something in ~/Library/Logs? -- Martin -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Octave (developer srcs) builds, but results in bus-error
On Nov 22, 2009, at 10:09 AM, Martin Costabel wrote: Ben Abbott wrote: On Nov 21, 2009, at 4:25 PM, Martin Costabel wrote: Ben Abbott wrote: [] Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x 0x02c0702f in std::locale::operator= () (gdb) Maybe a backtrace bt would give some more insight. -- Martin ... or maybe not :-( (gdb) bt No stack. Did the CrashReporter write something in ~/Library/Logs? -- Martin I pulled some additional changes for Octave yesterday. Now gdb gives a bit more info. .warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/loaders/.libs/libltdl_libltdl_la-preopen.o - no debug information available for libltdl/loaders/preopen.c. warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/.libs/libltdl_libltdl_la-lt__alloc.o - no debug information available for libltdl/lt__alloc.c. warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/.libs/libltdl_libltdl_la-lt_dlloader.o - no debug information available for libltdl/lt_dlloader.c. warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/.libs/libltdl_libltdl_la-lt_error.o - no debug information available for libltdl/lt_error.c. warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/.libs/libltdl_libltdl_la-ltdl.o - no debug information available for libltdl/ltdl.c. warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/.libs/libltdl_libltdl_la-slist.o - no debug information available for libltdl/slist.c. warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/.libs/argz.o - no debug information available for libltdl/argz.c. warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/.libs/libltdlS.o - no debug information available for libltdlS.c. warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/.libs/libltdl.lax/dlopen.a/dlopen.o - no debug information available for libltdl/loaders/dlopen.c. . done Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x 0x02c0702f in std::locale::operator= () (gdb) bt #0 0x02c0702f in std::locale::operator= () #1 0x02c05c9e in std::ios_base::_M_init () #2 0x02c1b25a in std::basic_ioschar, std::char_traitschar ::init () #3 0x0014ef23 in global constructors keyed to pager.cc () at ostream:362 #4 0x8fe0ed6d in __dyld__ZN16ImageLoaderMachO18doModInitFunctionsERKN11ImageLoader11LinkContextE () #5 0x8fe0d31e in __dyld__ZN11ImageLoader23recursiveInitializationERKNS_11LinkContextEj () #6 0x8fe0d2c2 in __dyld__ZN11ImageLoader23recursiveInitializationERKNS_11LinkContextEj () #7 0x8fe0d3d1 in __dyld__ZN11ImageLoader15runInitializersERKNS_11LinkContextE () #8 0x8fe024a9 in __dyld__ZN4dyld24initializeMainExecutableEv () #9 0x8fe07950 in __dyld__ZN4dyld5_mainEPK12macho_headermiPPKcS5_S5_ () #10 0x8fe018b1 in __dyld__ZN13dyldbootstrap5startEPK12macho_headeriPPKcl () #11 0x8fe01057 in __dyld__dyld_start () The file below is from ~/Library/Logs/DiagnosticReports. Ben octave_2009-11-22-141641_ben-abbotts-macbook-pro.crash Description: Binary data -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Octave (developer srcs) builds, but results in bus-error
On Nov 17, 2009, at 3:53 AM, Martin Costabel wrote: [I migrated my 10.5 Fink to 10.6 (using 32bit), and deleted my static libs left over from 10.5, and rebuilt them as needed]. Octave does build, but when I try to run it ... $ ./run-octave Bus error Now this is a different story. It should go into a different thread (once there is more information from the crash log). -- Martin Ok, I'm starting a new thread. I've attempted to run octave inside gdb. There are may complaints of no debug information. The final part is ... .warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/loaders/.libs/libltdl_libltdl_la-preopen.o - no debug information available for libltdl/loaders/preopen.c. warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/.libs/libltdl_libltdl_la-lt__alloc.o - no debug information available for libltdl/lt__alloc.c. warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/.libs/libltdl_libltdl_la-lt_dlloader.o - no debug information available for libltdl/lt_dlloader.c. warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/.libs/libltdl_libltdl_la-lt_error.o - no debug information available for libltdl/lt_error.c. warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/.libs/libltdl_libltdl_la-ltdl.o - no debug information available for libltdl/ltdl.c. warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/.libs/libltdl_libltdl_la-slist.o - no debug information available for libltdl/slist.c. warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/.libs/argz.o - no debug information available for libltdl/argz.c. warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/.libs/libltdlS.o - no debug information available for libltdlS.c. warning: Could not find object file /sw/src/fink.build/libtool2-2.2.6-3/libtool-2.2.6/libltdl/.libs/libltdl.lax/dlopen.a/dlopen.o - no debug information available for libltdl/loaders/dlopen.c. . done Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x 0x02c0702f in std::locale::operator= () (gdb) In the last few weeks, Octave modified how it configures and builds. One of the changes is the use of libtool. Does anyone have any insight as to what the problem might be? Ben -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Octave (developer srcs) builds, but results in bus-error
Ben Abbott wrote: [] Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x 0x02c0702f in std::locale::operator= () (gdb) Maybe a backtrace bt would give some more insight. -- Martin -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Octave (developer srcs) builds, but results in bus-error
On Nov 21, 2009, at 4:25 PM, Martin Costabel wrote: Ben Abbott wrote: [] Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x 0x02c0702f in std::locale::operator= () (gdb) Maybe a backtrace bt would give some more insight. -- Martin ... or maybe not :-( (gdb) bt No stack. Ben -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
