aha! i discovered what happens.
it's not that ladspa loading have been changed recently. i can
reproduce exactly the same if i define LADSPA_PATH=/usr/bin
it seems that qt-mt.so "looks like" a ladspa so clam tries to
load it. interesting!
so try changing LADPA_PATH
pau
En/na David García Garzón ha escrit:
That says that the application crashes when loading the Ladspa plugins.
Do you have the Ladspa path pointing to any non standard path? Ladspa loading
has been changed recently on the svn. Are you using svn or 1.0?
On Dijous 29 Març 2007, Michael Iber wrote:
the location of libqt-mt.so.3 seems to be a speciality of opensuse,
how can I force the programme to use the qt4 -version?
bt gives me:
(gdb) bt
#0 0xb503ff0f in QMutexPool::get () from /usr/local/lib/libqt-mt.so.3
#1 0xb4d6e6ba in QMetaObjectCleanUp::QMetaObjectCleanUp () from
/usr/local/lib/libqt-mt.so.3
#2 0xb50ef02a in QMotifStyle::qt_static_property () from
/usr/local/lib/libqt-mt.so.3
#3 0xb50ef3c5 in QMotifStyle::metaObject () from
/usr/local/lib/libqt-mt.so.3
#4 0xb4c8a60d in _init () from /usr/local/lib/libqt-mt.so.3
#5 0xb7fe43e3 in call_init () from /lib/ld-linux.so.2
#6 0xb7fe44f3 in _dl_init_internal () from /lib/ld-linux.so.2
#7 0xb7fe7ff6 in dl_open_worker () from /lib/ld-linux.so.2
#8 0xb7fe4026 in _dl_catch_error () from /lib/ld-linux.so.2
#9 0xb7fe7929 in _dl_open () from /lib/ld-linux.so.2
#10 0xb6e4395d in dlopen_doit () from /lib/libdl.so.2
#11 0xb7fe4026 in _dl_catch_error () from /lib/ld-linux.so.2
#12 0xb6e431dc in _dlerror_run () from /lib/libdl.so.2
#13 0xb6e439df in [EMAIL PROTECTED] () from /lib/libdl.so.2
#14 0xb7f5f167 in CLAM::LadspaPluginsExplorer::GetList () from
/usr/local/lib/libclam_core.so.1
#15 0x0810c92d in ProcessingTree (this=0x834bef8, parent=0x825c4f8) at
src/ProcessingTree.cxx:165
#16 0x081200c3 in MainWindow (this=0xbfc069d4) at src/MainWindow.hxx:58
#17 0x0811759d in main (argc=1, argv=0xbfc06ba4) at src/main.cxx:67
(gdb)
David García Garzón schrieb:
If you could type the 'bt' command on gdb it will give you the backtrace
of call on the crash point, which is even useful.
At first sight, it is strange to see qt-mt linking against the
NetworkEditor. qt-mt is Qt3 and NetworkEditor should link just with Qt4.
Also the path for suchs library is not a tipical one:
/usr/local/lib/libqt-mt.so.3 so. Any mess with local library
installation?
David.
On Dijous 29 Març 2007, Michael Iber wrote:
gdb run gives the following output:
(gdb) run
Starting program: /usr/bin/NetworkEditor
Failed to read a valid object file image from memory.
[Thread debugging using libthread_db enabled]
[New Thread -1247086896 (LWP 6719)]
warning: Lowest section in /usr/lib/libicudata.so.34 is .hash at
000000b4 EXPLORER warning: trying to open non ladspa plugin:
/usr/lib/ladspa/blop_files
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1247086896 (LWP 6719)]
0xb5016f0f in QMutexPool::get () from /usr/local/lib/libqt-mt.so.3
(gdb) Quit
(gdb) Quit
David García Garzón schrieb:
Could you give us some backtrace, the console output or something that
might be usefull to fix that problem?
On Dijous 29 Març 2007, Michael Iber wrote:
Hello,
NetworkEditor crashes (seg fault) at startup with packman-distro and
successfully self-compiled 1.0. version. Any ideas, what could be the
reason for that (openSuse 10.2. with jad-(jacklab.net)-rt-kernel)?
Thanks a lot, I really would like to get into this very interesting
concept .....
cheers,
Michael
------------------------------------------------------------------------
_______________________________________________
CLAM mailing list
[email protected]
http://www.iua.upf.es/mtg/clam
_______________________________________________
CLAM mailing list
[email protected]
http://www.iua.upf.es/mtg/clam
