GNOME Bugzilla – Bug 709460
Easytag Segmentation fault
Last modified: 2013-10-05 13:05:03 UTC
Easytag 2.1.8 crashes, under KDE 4.11.1, Sabayon 64 bit, when I press right mouse button in Dolphin, on a folder, Open With, EasyTag or I simply run from the command line (replace <path here> by the real path): easytag '<path here>' Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. EasyTAG version 2.1.8: Abnormal exit (PID: 16155). Received signal SIGSEGV (11) You have probably found a bug in EasyTAG. Please, file a bug report with a GDB backtrace ('gdb easytag core' then 'bt' and 'l') and information to reproduce it at: https://bugzilla.gnome.org/enter_bug.cgi?product=easytag Segmentation fault
Please file a bug report with a GDB backtrace ('gdb easytag core' then 'bt' and 'l'). As written in the output.
Ok, bt I don't think it's enough: gdb easytag '<path here>' GNU gdb (Gentoo 7.5.1 p2) 7.5.1 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". For bug reporting instructions, please see: <http://bugs.gentoo.org/>... Reading symbols from /usr/bin/easytag...Reading symbols from /usr/lib64/debug/usr/bin/easytag.debug...done. done. <path here>: No such file or directory. (gdb) bt No stack. (gdb) l 164 src/easytag.c: No such file or directory. (gdb) q
gdb --args easytag '<path here>' gives me the same. I have the debug symbols for easytag and glibc installed.
Is this right below? It doesn't crash in gdb, only standalone. gdb easytag core GNU gdb (Gentoo 7.5.1 p2) 7.5.1 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". For bug reporting instructions, please see: <http://bugs.gentoo.org/>... Reading symbols from /usr/bin/easytag...Reading symbols from /usr/lib64/debug/usr/bin/easytag.debug...done. done. /home/admius/core: No such file or directory. (gdb) set args '<path here>' (gdb) run Starting program: /usr/bin/easytag '<path here>' warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffff7ffa000 warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffe81eb700 (LWP 14429)] Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. [New Thread 0x7fffe6d21700 (LWP 14430)] [Thread 0x7fffe6d21700 (LWP 14430) exited] [Thread 0x7ffff7f838c0 (LWP 14423) exited] [Inferior 1 (process 14423) exited normally] (gdb) q
One more, now it scans the current directory (passed as argument), then starts scanning from '/'.
Thanks for the bug report. In order to get a core dump, you probably have to change some settings: http://www.gentoo.org/proj/en/qa/backtraces.xml#doc_chap1_sect6 This particular bug was fixed in master in commit 26eb6308fd0e8681728b72f9559598e59847a359 soon after 2.1.8 was released: https://git.gnome.org/browse/easytag/commit/?id=26eb6308fd0e8681728b72f9559598e59847a359 The fix will be in the upcoming 2.1.9 release. *** This bug has been marked as a duplicate of bug 693613 ***
I can't make it crash under gdb. The core dump is not an option - I use Sabayon in order to avoid compiling everything, kernel being the most delicate thing. I really have not enough knowledge of how to configure it. I've tried in the past and it was a mess. Anyway, the OS reports it's unlimited. Thing is, now it crashes when no debug, and this is weird. It could be something in the installation itself that it is skipped in one case or the other.