Bug 142 - Segmentation fault when RESET command occures
Summary: Segmentation fault when RESET command occures
Status: CLOSED FIXED
Alias: None
Product: LinuxSampler
Classification: Unclassified
Component: other (show other bugs)
Version: SVN Trunk
Hardware: PC Linux
: P2 normal
Assignee: Christian Schoenebeck
URL:
Depends on:
Blocks:
 
Reported: 2010-02-17 17:08 CET by Nikita Zlobin
Modified: 2013-05-31 19:43 CEST (History)
0 users

See Also:


Attachments
backtrace (60.05 KB, application/x-gzip)
2010-02-27 18:34 CET, Christian Schoenebeck
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nikita Zlobin 2010-02-17 17:08:13 CET
How to reproduce: simply launch linuxsampler, frontend and send "RESET" command (I made it using telnet).
<--------------(
(gdb) run
Starting program: /usr/local/bin/linuxsampler
[Thread debugging using libthread_db enabled]
LinuxSampler 1.0.0.cvs3
Copyright (C) 2003,2004 by Benno Senoner and Christian Schoenebeck
Copyright (C) 2005-2009 Christian Schoenebeck
Detected features: MMX SSE SSE2
Automatic Stacktrace: Off
Creating Sampler...OK
Registered sampler engines: 'GIG','SF2','SFZ'
Registered MIDI input drivers: ALSA,JACK
Registered audio output drivers: ALSA,JACK
Loading instrument editor plugins...[New Thread 0xb78a8700 (LWP 9926)]
OK
Registered instrument editors: 'gigedit'
Starting LSCP network server (0.0.0.0:8888)...[New Thread 0xb658bb90 (LWP 9929)]
OK
LinuxSampler initialization completed. :-)

LSCPServer: Client connection established on socket:6.
Unloading instrument editor plugins...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb658bb90 (LWP 9929)]
0xb7ebf283 in std::_Rb_tree<LinuxSampler::gig::Engine*, LinuxSampler::gig::Engine*, 
std::_Identity<LinuxSampler::gig::Engine*>, std::less<LinuxSampler::gig::Engine*>, 
std::allocator<LinuxSampler::gig::Engine*> >::_M_erase (this=0xb67301a0, __x=0xb67301a0) at 
/usr/include/c++/4.3/bits/stl_tree.h:936
936	    _M_erase(_Link_type __x)
(gdb) quit
The program is running.  Exit anyway? (y or n) y
)------>
I am not sure, but asume, that LS 1.0 release log also may be useful (only some tail):
<--------------------------(
[New Thread 0xb663eb90 (LWP 10331)]
[Thread 0xb663eb90 (LWP 10331) exited]
Unloading instrument editor plugins...Inconsistency detected by ld.so: dl-close.c: 719: _dl_close: Assertion 
`map->l_init_called' failed!

Program exited with code 0177.
)-------------------------->
Comment 1 Christian Schoenebeck 2010-02-27 18:34:52 CET
Created attachment 54 [details]
backtrace

Uploaded for Mike Cookson, sent by Email.
Comment 2 Christian Schoenebeck 2013-05-31 19:43:37 CEST
AFAIK this bug has been fixed. Closing this report now. Feel free to reopen this report in case this problem still exists.