From: Karl W. <kar...@gm...> - 2011-05-18 10:28:03
|
Hi William, The -f argument prevents it from running any system-wide octaverc files, so yes its the same as commenting out the pkg commands. But it looks like there still might be another issue here. I can reproduce the multi_import error in valgrind with the SWIG 1.3.40 test suite (using Octave 3.2.4), so it doesn't look like it was caused by my patches. Unfortunately I'm not familiar enough with the Octave module to have any further ideas :( Cheers, Karl On 18 May 2011 02:36, William S Fulton <ws...@fu...> wrote: > On 17/05/11 21:31, Karl Wette wrote: >> >> Hi William, >> >> I think I've seen this problem before. Try modifying the Makefile to >> run octave with the options "-qf" instead of just "-q". >> > -qf removes the "Invalid free() / delete / delete[]" valgrind error in the > mods and multi_import testcases and I havn't seen it crash, although > previously it crashed erratically. I'll check this change in. However, the > imports testcase still has the valgrind error and crashes on Ubuntu Maverick > (Octave 3.2.4). > > Ubuntu Natty still doesn't run anything - it has the "Inconsistency detected > by ld.so: dl-close.c: 737: _dl_close: Assertion `map->l_init_called' > failed!" error we discussed beforehand even with -qf :( > >> There appears to be some strange interaction between SWIG modules and >> the Octave package manager "pkg", which executes some commands in the >> system-wide octaverc (at least for version 3.2.4 on debian squeeze). I >> found that if I comment out either of these lines in the octaverc: >> >> pkg global_list /usr/share/octave/packages/3.2/octave_packages; >> or >> pkg load auto; >> > Does this have the same effect as -qf then? > >> Octave no longer crashes on exit. I have no idea whether this is a >> SWIG bug or an Octave bug. >> > > William > |