Your message dated Fri, 12 May 2006 16:59:04 -0400
with message-id <[EMAIL PROTECTED]>
and subject line artsd SEGV on artsbuilder executes
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libarts1
Version: 1.1.1-2
Artsd SEGV on executing any example module of the artsbuilder.
According to gdb at:
/usr/include/kde/arts/dynamicskeleton.h line 116:
class DynamicSkeleton : virtual public Parent_skel, public
DynamicSkeletonBase
{
public:
/**
* constructor
*/
DynamicSkeleton(const std::string& interface)
: DynamicSkeletonBase(this, interface,
Parent_skel::_interfaceNameSkel())
{
//
}
...
It was called by SynthModule_dskel(structureDesc.name()) in the
Structure_impl constructor.
It rarely got through the constructor
DynamicSkeletonBase::DynamicSkeletonBase(Object_skel *skel,
const std::string& interfaceName, const std::string&
interfaceNameParent)
The suspect is the interfaceNameParent reference in the constructor. It
is defined as const std::string&.
If we look at mcop/artsflow.cc generated by the mcopidl, we are
eventually calling methods like this:
std::string Arts::SynthModule_skel::_interfaceNameSkel()
{
return "Arts::SynthModule";
}
It is the same for all other modules.
On a test program and g++-3.2.3, it would warn us about "returning
reference to temporary" on compilation. The exec would SEGVwhen we make
use of the return.
Regards.
P.C. Chan
--- End Message ---
--- Begin Message ---
This seems to work now, but if you're still having the problem, do let
us know. Thanks.
--- End Message ---
