Yaroslav Halchenko wrote:
Wow -- nice finding Fabian!
I wonder what should be the resolution... and why even the confusion
since shogun's SVC_Q lies in shogun space (not sure how well that is
represented in dynamic library, or may be on your box shogun/libsvm and
pymvpa were built with DYLD_FORCE_FLAT_NAMESPACE or smth like that)
Unfortunately it isn't the case of the segfaults I can reproduce :-/
(if you have a moment/desire -- try running the unittests extract which
supposed to trigger it)
Thanks Yaroslav for your help. It's probably a miscompilation issue on
my part (I'm doing some LibSVM development), so I wouldn't spend much
time on this.
I'll update my system (macports), and I'll insist if the problem persists.
Thanks,
fabian
On Tue, 09 Mar 2010, Fabian Pedregosa wrote:
Thanks for looking at this. I solved the problem by uninstalling
shogun. It seems the problem was due to name clashing between libsvm
& shogun. The stack trace is interesting:
0 libshogun.4.dylib 0x03f87656 SVC_Q::get_Q(int, int)
const + 54
1 libsvm.dylib 0x0425ecd9
Solver::select_working_set(int&, int&) + 777
2 libsvm.dylib 0x0426109a Solver::Solve(int,
QMatrix const&, double const*, signed char const*, double*, double,
double, double, Solver::SolutionInfo*, int) + 778
which means it 'jumps' from libsvm to shogun (I have no clue why
this happens)
------------------------------------------------------------------------
_______________________________________________
Pkg-ExpPsy-PyMVPA mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-exppsy-pymvpa
_______________________________________________
Pkg-ExpPsy-PyMVPA mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-exppsy-pymvpa
