Bug 78764 - timidity crash in artsc binding
Summary: timidity crash in artsc binding
Status: RESOLVED DUPLICATE of bug 62603
Alias: None
Product: arts
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Stefan Westerfeld
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-30 22:27 UTC by Casteyde.Christian
Modified: 2005-04-12 05:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Casteyde.Christian 2004-03-30 22:27:53 UTC
Version:            (using KDE KDE 3.2.1)
Installed from:    Compiled From Sources
OS:          Linux

Starting Timidity 2.13 with -OR option to use arts backend crashes timidity in arts backend code. Was familiar with timidity code and I'm quite confident it didn't crashed with KDE 3.1. However, didn't tried regression test.

Following is the backtrace (from gdb) :

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 32367)]
0x40907446 in Arts::StartupManager::startup() () from /opt/kde/lib/libmcop.so.1
(gdb) bt
#0  0x40907446 in Arts::StartupManager::startup() ()
   from /opt/kde/lib/libmcop.so.1
#1  0x408e5a3a in Arts::Dispatcher::Dispatcher(Arts::IOManager*, Arts::Dispatcher::StartServer) () from /opt/kde/lib/libmcop.so.1
#2  0x4070bd22 in arts_backend_init () from /opt/kde/lib/libartscbackend.so.0
#3  0x402107e2 in arts_init () from /opt/kde/lib/libartsc.so.0
#4  0x080e6f18 in open_output ()
#5  0x080de8f0 in timidity_play_main ()
#6  0x080dee51 in main ()
#7  0x40420d06 in __libc_start_main () from /lib/libc.so.6

Sorry, wasn't compiled with debug info, could do it if necessary (if one give me the configure option for arts).

System deps :
Linux 2.6.4 / OSS driver (however Alsa lib 1.0.3 installed)
gcc 3.3.3, -O2 -march=athlon.

Thanks,
CC
Comment 1 Bastien Nocera 2004-04-06 00:01:37 UTC
This is a dupe of #62603.
Comment 2 Maksim Orlovich 2005-04-12 05:44:41 UTC
Indeed, thank you. 

*** This bug has been marked as a duplicate of 62603 ***