Segfault in Gnomad2 2.8.2
Brought to you by:
snirkel
Menu
▾
▴
#252 Segfault in Gnomad2 2.8.2
GNU gdb (GDB) 7.0-ubuntu
Copyright (C) 2009 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-linux-gnu".
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/gnomad2...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/gnomad2
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffeef69910 (LWP 2942)]
[Thread 0x7fffeef69910 (LWP 2942) exited]
[New Thread 0x7fffeef69910 (LWP 2943)]
[Thread 0x7fffeef69910 (LWP 2943) exited]
Queried Creative ZEN
[New Thread 0x7fffeef69910 (LWP 2944)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffeef69910 (LWP 2944)]
0x0000000000412b0b in ?? ()
(gdb) backtrace
0 0x0000000000412b0b in ?? ()
1 0x00007ffff4f16b44 in ?? () from /lib/libglib-2.0.so.0
2 0x00007ffff4429a04 in start_thread (arg=<value optimized="" out="">) at pthread_create.c:300</value>
3 0x00007ffff419380d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
4 0x0000000000000000 in ?? ()
(gdb) finish
Run till exit from #0 0x0000000000412b0b in ?? ()
[Thread 0x7fffeef69910 (LWP 2944) exited]
Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
gnomad2 -D 15
adding song "Dance" to songhash...
---- Song metadata -----
Artist: ZEN Demo Artists
Title: Dance
Album: ZEN Demo Songs
Year: 2007
Genre: Pop
Length: 1:39
Size: 2425443 bytes
Codec: WAV
Track#: 1
Protected: NO
Filename: 01 Dance.mp3
Path: 1665
Folder: (null)
Segmentation fault
I recently made a thorough overhaul of Gnomad2, removing many bugs, as a result I think it has been re-adopted to Debian (it was staged for removal). Can you please try the 2.9.6 version and see if the problem persists?