Your message dated Thu, 8 Oct 2015 20:58:16 +0200 with message-id <[email protected]> and subject line Re: Bug#798850: enfuse: Immediate segmentation fault on launch has caused the Debian Bug report #798850, regarding enfuse: Immediate segmentation fault on launch to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 798850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798850 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: enfuse Version: 4.1.3+dfsg-2 Severity: grave Justification: renders package unusable -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-amd64 (SMP w/6 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages enfuse depends on: ii libboost-filesystem1.55.0 1.55.0+dfsg-4 ii libboost-system1.55.0 1.55.0+dfsg-4 ii libc6 2.19-19 ii libgcc1 1:5.2.1-16 ii libgomp1 5.2.1-16 ii libgsl0ldbl 1.16+dfsg-4 ii liblcms2-2 2.6-3+b3 ii libstdc++6 5.2.1-16 ii libtiff5 4.0.5-1 ii libvigraimpex4 1.9.0+dfsg-10+b3 Versions of packages enfuse recommends: ii hugin 2015.0.0~rc3+dfsg-1+b1 enfuse suggests no packages. -- no debconf information When I invoke enfuse it aborts immediately with a segmentation fault. This is independent of the specified input files. Gdb backtrace: Starting program: /usr/bin/enfuse *expo* [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Program received signal SIGSEGV, Segmentation fault. 0x00007ffff695562b in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #0 0x00007ffff695562b in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #1 0x0000000000450eaa in ?? () #2 0x00000000004088c5 in ?? () #3 0x00007ffff5dccb45 in __libc_start_main (main=0x4085a0, argc=4, argv=0x7fffffffe278, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe268) at libc-start.c:287 #4 0x000000000040c33e in ?? ()
--- End Message ---
--- Begin Message ---On 2015-09-13 Simon Frei <[email protected]> wrote: [...] > When I invoke enfuse it aborts immediately with a segmentation > fault. This is independent of the specified input files. Hello, this bug was caused by the gcc5 transition and was resolved by a rebuild against libvigraimpex5v5, which has now reached testing. Closing. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
--- End Message ---
