#763 segmentation fault in libdl when starting tulip

[Alexey Stukalov]

When starting tulip, the first library (librevereseedges) is loaded correctly, then on libogdfvisibility it crashes in libdl.so:

#0  0x00007ffff7dea9c8 in call_init.part () from /lib64/ld-linux-x86-64.so.2
#1  0x00007ffff7deaab3 in _dl_init_internal () from /lib64/ld-linux-x86-64.so.2
#2  0x00007ffff7deec08 in dl_open_worker () from /lib64/ld-linux-x86-64.so.2
#3  0x00007ffff7dea884 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2
#4  0x00007ffff7dee3fb in _dl_open () from /lib64/ld-linux-x86-64.so.2
#5  0x00007ffff077402b in ?? () from /usr/lib/libdl.so.2
#6  0x00007ffff7dea884 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2
#7  0x00007ffff07745dd in ?? () from /usr/lib/libdl.so.2
#8  0x00007ffff07740c1 in dlopen () from /usr/lib/libdl.so.2
#9  0x00007ffff79cf070 in tlp::PluginLibraryLoader::loadPluginLibrary (filename=..., loader=0xb58620)
    at /home/astukalov/projects/tulip/tulip-src/library/tulip-core/src/PluginLibraryLoader.cpp:120
#10 0x00007ffff79cf51b in tlp::PluginLibraryLoader::initPluginDir (this=0x79c030, loader=0xb58620)
    at /home/astukalov/projects/tulip/tulip-src/library/tulip-core/src/PluginLibraryLoader.cpp:259
#11 0x00007ffff79cee8a in tlp::PluginLibraryLoader::loadPlugins (loader=0xb58620, folder=...)
    at /home/astukalov/projects/tulip/tulip-src/library/tulip-core/src/PluginLibraryLoader.cpp:67
#12 0x00007ffff710e41f in tlp::initTulipSoftware (loader=0xb58620, removeDiscardedPlugins=true)
    at /home/astukalov/projects/tulip/tulip-src/library/tulip-gui/src/TlpQtTools.cpp:332
#13 0x0000000000445a5a in main (argc=1, argv=0x7fffffffe368)
    at /home/astukalov/projects/tulip/tulip-src/software/tulip/src/main.cpp:169

Interestingly, when installed into /opt/tulip with the same configuration options this does not happen. This happens with Tulip 4.5.0 and the latest gcc stack (4.8.2), ArchLinux, but it was also happening with at least versions 4.3.0 and 4.4.0.

I'm aware that it's a known issue that was also observed on Debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723982), and that libdl should in any case not segfault like this. Nevertheless, maybe it's still possible to introduce some workaround into Tulip, because that bugs blocks me from working with tulip code and developing plugins?

[Antoine Lambert]

Hi Alexey,

I remember having a smilar issue with GCC 4.7.3 on Ubuntu 13.04 64bits,
Tulip was crashing when loading OGDF related plugins.
The workaround I used was to disable compiler optimizations
when compiling the OGDF library.

That workaround is still present in the following file in the Tulip source tree: thirdparty/OGDF/CMakeLists.txt (lines 32 to 42). You can try to change the GCC version line 39, recompile and see if it solves the issue.

Hope that it will helps,

Antoine

[Patrick Mary]

I'm sorry but at this time we got no workaround,
except a downgrade of gcc or a removal of the libogdf*.so libraries
from the tulip installed libraries (if you do not need the OGDF plugins).
Hope this helps.

[Alexey Stukalov]

Thanks, Antoine. I've tried modifying CMakeLists.txt so that -O0 is added for gcc 4.8.2 (both debug and release) as you suggested, but there was no change. Actually, I have also tried compiling with clang++ before. It compiles, but still crashes in the same way.

[Antoine Lambert]

Hi Alexey,

That bug is now fixed in the current tulip trunk (see revision 10148)

Cheers

[Patrick Mary]

This bug is now fixed in the current svn code line (commit #10148).