gwave crashed with SIGSEGV in scm_string_hash()

Bug #1302586 reported by Perfecto
44
This bug affects 9 people
Affects Status Importance Assigned to Milestone
gwave (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Nothing more

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gwave 20090213-4
ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
Uname: Linux 3.13.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Apr 4 14:43:58 2014
ExecutablePath: /usr/bin/gwave
InstallationDate: Installed on 2013-09-14 (202 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130903)
ProcCmdline: gwave
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7feaa87caacc <scm_string_hash+28>: movzbl -0x1(%rdi),%edx
 PC (0x7feaa87caacc) ok
 source "-0x1(%rdi)" (0x00000005) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gwave
StacktraceTop:
 scm_string_hash () from /usr/lib/libguile.so.17
 scm_string_to_symbol () from /usr/lib/libguile.so.17
 scm_init_gnome_gobject_types () from /usr/lib/libguile-gnome-gobject-2.so.0
 scm_dynamic_call () from /usr/lib/libguile.so.17
 ?? () from /usr/lib/libguile.so.17
Title: gwave crashed with SIGSEGV in scm_string_hash()
UpgradeStatus: Upgraded to trusty on 2014-03-24 (10 days ago)
UserGroups: adm audio avahi avahi-autoipd backup bluetooth bumblebee cdrom crontab dialout dip disk fax floppy fuse games list lp lpadmin mail netdev ntp pcscd plugdev sambashare saned scanner src sudo tape tty users video voice

Revision history for this message
Perfecto (perfecto) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 scm_string_hash (str=0x6 <Address 0x6 out of bounds>, str@entry=0x5 <Address 0x5 out of bounds>, len=4, len@entry=5) at hash.c:48
 scm_i_mem2symbol (str=0x7feaa8c79380 <scm_sym_gtype_string_raw_cell>) at symbols.c:164
 scm_string_to_symbol (string=string@entry=0x7feaa8c79380 <scm_sym_gtype_string_raw_cell>) at symbols.c:281
 scm_init_gnome_gobject_types () at gtype.x:2
 scm_dynamic_call (func=0x1ffaaa29ba242, dobj=0x7fea9e254220) at dynl.c:266

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gwave (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gwave (Ubuntu):
status: New → Confirmed
Revision history for this message
Vassili Leonov (vleolml) wrote :

I'm experincing the same bug
cat /var/crash/_usr_bin_gwave.1000.crash:
...
SegvAnalysis:
 Segfault happened at: 0x7f9e82582acc <scm_string_hash+28>: movzbl -0x1(%rdi),%edx
...

On:
Ubuntu 14.04.1 LTS
$ uname -r
3.13.0-35-generic
$ uname -i
x86_64

apt-get update; apt-get upgrade
$ LC_ALL=en_US date
Wed Sep 3 20:35:48 MSK 2014

dpkg -p gwave
...
Architecture: amd64
Version: 20090213-4

dpkg -p guile-1.8-libs
Architecture: amd64
Version: 1.8.8+1-8ubuntu3

dpkg -p guile-gnome2-glib
...
Architecture: amd64
Version: 2.16.2-1.1ubuntu1

Revision history for this message
Vassili Leonov (vleolml) wrote :

The root cause of this bug is that gwave is long unmaintained and is built with obsolete quile-1.8, whereas the rest of the system, and in particular guile-gnome2-glib is built with quile-2.0.

When rebuilding gwave from source I'm getting the very same core dump behavior. The right thing to do is to upgrade gwave to use quile-2.0, avoiding quile-1.8 completely, also quile-1.8 is being obsolted upstream.

On top of that gwave autoconf (configure.ac) is not well written in relation to up to date version of guile-gnome2 , so cleaning up that area would help a lot as well.

Revision history for this message
giuliano69 (giuliano-lotta) wrote :

could be GTKview a valid alternative ?

Revision history for this message
Sergio Callegari (callegar) wrote :

Has stayed totally broken for many years and release cycles. How about getting rid of gwave for good?

Revision history for this message
Phonon (stephanstrauss) wrote :

Sad, that there is still no solution -- can we help. I have no idea, where to start, but if you need a helping hand, write me.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.