On Wed, 28 Oct 2009 08:50:43 -0400
John Lindgren wrote:
> Oops, I didn't look at the backtrace close enough. It's thread 1 that
> had the segmentation fault (address 0xb7da075a). It looks like
> cuesheet_ng.so is fine and timidity.so is the culprit.
After reading that, as 'root' I did:
Notes for one-liner fans. "Here" files are OK, but a one-liner is easiest to
copy & paste.
After a bit of trial & error, I came up with:
# Run 'empty' on 'gdb -q audacious2' to automate 'gdb' session.
# Output results to a temp file.
empty -f -L /tmp/e.log gdb -q audacio
On Tue, 2009-10-27 at 15:51 -0400, A. Costa wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0xb7da075a in ?? () from /lib/libglib-2.0.so.0
> (gdb)
> Thread 3 (Thread 0xb187cb70 (LWP 7707)):
> #0 0xb7fe2424 in __kernel_vsyscall ()
> #1 0xb75f0cc
On Wed, 28 Oct 2009, A. Costa wrote:
Thread 1 (Thread 0xb7137a40 (LWP 11836)):
#0 0xb7da075a in ?? () from /lib/libglib-2.0.so.0
#1 0xb7da0faf in g_filename_from_uri () from /lib/libglib-2.0.so.0
#2 0xb7fb59f5 in vfs_file_test () from /usr/lib/libaudcore.so.1
On Wed, 2009-10-28 at 01:41 -0400, A. Costa wrote:
> I wasn't sure how to remove 'cuesheet_ng', since the setup menu
> requires first starting 'audacious2'. So as 'root' I moved
> 'cuesheet_ng' to '/tmp':
>
> # find it
> % dlocate cuesheet_ng
> audacious-plugins-extra: /usr/lib/
On Tue, 27 Oct 2009 22:26:25 -0400
John Lindgren wrote:
> > Program received signal SIGSEGV, Segmentation fault.
> > 0xb7da075a in ?? () from /lib/libglib-2.0.so.0
> > (gdb)
> > Thread 3 (Thread 0xb187cb70 (LWP 7707)):
> > #0 0xb7fe2424 in __kernel_vsyscall ()
> > #1 0x
On Tue, 27 Oct 2009 07:18:32 -0400
John Lindgren wrote:
> On Tue, 2009-10-27 at 03:06 -0400, A. Costa wrote:
> > Sorry, but I'm not up on debuggers (for 'audacious' anyway). What
> > would I type at the command line? A one-liner would be ideal for
> > copy & pasting.
>
> $ gdb audacious2
> (gd
On Tue, 2009-10-27 at 03:06 -0400, A. Costa wrote:
> Sorry, but I'm not up on debuggers (for 'audacious' anyway). What
> would I type at the command line? A one-liner would be ideal for copy
> & pasting.
$ gdb audacious2
(gdb) run
Then, when it crashes:
(gdb) thread apply all backtrace
Peace,
On Sun, 25 Oct 2009 19:26:26 -0400
John Lindgren wrote:
> strace is good for tracking disk access, but not so good for a
> segmentation fault. Please send a debugger backtrace.
Sorry, but I'm not up on debuggers (for 'audacious' anyway). What
would I type at the command line? A one-liner woul
A. Costa wrote:
> Package: audacious
> Version: 2.1-1+b1
> Severity: normal
>
>
> It's been broken at least a month here...
>
> % audacious2 ; echo $?
> Segmentation fault
> 139
>
> Attached is the bzip2'd output of:
>
> % strace -o /tmp/audacious.segfault.log audacious2
strac
tags 491615 - moreinfo
thanks
Neil McGovern wrote:
> Package: audacious
> Version: 1.5.1-4
> Followup-For: Bug #491615
>
> Seems that this is still present in i386:
...
Took me a while to notice your reply; would be nice if you could add my
email to the "To:" field.
Se
Package: audacious
Version: 2.1-1+b1
Severity: normal
It's been broken at least a month here...
% audacious2 ; echo $?
Segmentation fault
139
Attached is the bzip2'd output of:
% strace -o /tmp/audacious.segfault.log audacious2
HTH...
-- System Information:
Debian Release: sq
And that previous message was me, but it seems I didn't set the eamil
correctly...
Neil
--
Jump in and have a quim!
signature.asc
Description: Digital signature
Package: audacious
Version: 1.5.1-4
Followup-For: Bug #491615
Seems that this is still present in i386:
nmcgov...@nmcgovern:~$ gdb audacious
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
T
Tomasz,
Pardon my bad memory, since I think you replied to me off-list already.
Do you still get this crash with 1.5.1-4 or 2.0.1-1? Make sure to clear
$HOME/.config/audacious when you update, since running new versions with
old config files has been known to cause problems.
John Lindgren
--
Hi Tomasz,
Is it possible for you to check out the current upstream version, build
it, and see whether the problem stills occurs? Hopefully we can get this
problem fixed before 2.0 is released. Unfortunately, I don't have an
amd64 machine to test on.
John Lindgren
--
To UNSUBSCRIBE, email to
Package: audacious
Version: 1.5.1-4
Followup-For: Bug #491615
Starting program: /usr/bin/audacious
[Thread debugging using libthread_db enabled]
[New Thread 0x7f9712d06770 (LWP 25115)]
[New Thread 0x40daf950 (LWP 25118)]
amidi-plug(amidi-plug.c:amidiplug_init:97): init, read configuration
amidi
I found out that the problem is caused by audacious-crossfade. Remove
crossfade, maybe reinstall audacious and then install the newest version
of audacious-crossfade again, e.g. from
http://famous-timo.de/design4/home/pages/software/debian/audacious-crossfade_0.3.14-1_i386.deb
This works.
--
gdb said:
Breakpoint 2 at 0x805c345: file main.c, line 668.
Starting program: /usr/bin/audacious
[Thread debugging using libthread_db enabled]
[New Thread 0xb732b910 (LWP 5899)]
[Switching to Thread 0xb732b910 (LWP 5899)]
main (argc=Cannot access memory at address 0x0
) at main.c:668
668 main
Package: audacious
Version: 1.5.1-1
Severity: important
-- command lne information
[EMAIL PROTECTED]:~$ audacious
amidi-plug(amidi-plug.c:amidiplug_init:97): init, read configuration
amidi-plug(i_backend.c:i_backend_load:107): loading backend
'/usr/lib/audacious/Input/amidi-plug/ap-alsa.so'
amid
20 matches
Mail list logo
