[Gpe-list] Gpe-bugs Digest, Vol 30, Issue 2
gpe-bugs-request at linuxtogo.org
gpe-bugs-request at linuxtogo.org
Wed May 20 12:00:28 CEST 2009
Send Gpe-bugs mailing list submissions to
gpe-bugs at linuxtogo.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/gpe-bugs
or, via email, send a message with subject or body 'help' to
gpe-bugs-request at linuxtogo.org
You can reach the person managing the list at
gpe-bugs-owner at linuxtogo.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gpe-bugs digest..."
Today's Topics:
1. [Bug 281] New: 0.14 crashes if a sound file is specified
(bugzilla-daemon at linuxtogo.org)
2. [Bug 281] 0.14 crashes if a sound file is specified
(bugzilla-daemon at linuxtogo.org)
----------------------------------------------------------------------
Message: 1
Date: Tue, 19 May 2009 14:10:01 +0200
From: bugzilla-daemon at linuxtogo.org
Subject: [Gpe-bugs] [Bug 281] New: 0.14 crashes if a sound file is
specified
To: gpe-bugs at linuxtogo.org
Message-ID: <bug-281-7 at http.bugs.linuxtogo.org/>
Content-Type: text/plain; charset="UTF-8"
http://bugs.linuxtogo.org/show_bug.cgi?id=281
Summary: 0.14 crashes if a sound file is specified
Product: gpe-announce
Version: 0.13
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P4
Component: default
AssignedTo: gpe-bugs at linuxtogo.org
ReportedBy: codehelp at debian.org
Estimated Hours: 0.0
Created an attachment (id=69)
--> (http://bugs.linuxtogo.org/attachment.cgi?id=69)
bug-buddy backtrace report
I'm trying to test 0.14 for upload to Debian but whereas the plain buzzer
works, trying to specify a different sound file (and use the GStreamer
support), causes gpe-announce 0.14 to crash.
I suspect it is related to the build message:
callbacks.c: In function ?play_url?:
callbacks.c:475: warning: passing argument 1 of ?gst_bin_add_many? from
incompatible pointer type
gpe-announce-0.14$ ./gpe-announce "test" /usr/share/sounds/startup3.wav
Gstreamer library loaded
Cannot access memory at address 0x48d0b60f30245489
Killed
(gdb) run "test" /usr/share/sounds/startup3.wav
[Thread debugging using libthread_db enabled]
[New Thread 0x7f20f8728780 (LWP 8305)]
Gstreamer library loaded
[New Thread 0x7f20ef5f8950 (LWP 8308)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f20ef5f8950 (LWP 8308)]
0x0000000000000000 in ?? ()
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x0000000000403ecf in play_url ()
#2 0x00000000004042c3 in play_alarm ()
#3 0x00007f20f4ef3faa in start_thread (arg=<value optimized out>) at
pthread_create.c:300
#4 0x00007f20f4c6829d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5 0x0000000000000000 in ?? ()
Is there a reason why gpe-announce uses a dlopen for this functionality instead
of building against the gstreamer library and using the function calls
directly? (maybe using a ./configure switch so that this code is not loaded
unless built with the option enabled?)
I'm attaching the report from bug-buddy which is triggered each time.
A secondary problem is that any second argument to gpe-announce causes a crash,
whether that is a sound file or just junk. gpe-announce should check that the
second argument is a file before trying to pass that to gstreamer.
--
Configure bugmail: http://bugs.linuxtogo.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------
Message: 2
Date: Tue, 19 May 2009 14:23:04 +0200
From: bugzilla-daemon at linuxtogo.org
Subject: [Gpe-bugs] [Bug 281] 0.14 crashes if a sound file is
specified
To: gpe-bugs at linuxtogo.org
Message-ID: <E1M6OLY-00043K-2Q at linuxtogo.org>
Content-Type: text/plain; charset="UTF-8"
http://bugs.linuxtogo.org/show_bug.cgi?id=281
--- Comment #1 from Neil Williams <codehelp at debian.org> 2009-05-19 14:23:03 ---
I've simply commented out the argv[2] handling in main.c for now, leaving the
Debian package with only the default audio buzzer. Other Debian changes can be
viewed at:
http://patch-tracking.debian.net/package/gpe-announce/0.13-2
The latest changes will appear at:
http://patch-tracking.debian.net/package/gpe-announce/0.14-1
once the upload has been processed.
--
Configure bugmail: http://bugs.linuxtogo.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------
_______________________________________________
Gpe-bugs mailing list
Gpe-bugs at linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/gpe-bugs
End of Gpe-bugs Digest, Vol 30, Issue 2
***************************************
More information about the Gpe-list
mailing list