I’m guessing, but just calling DebugControl::Init may not be enough, especially because I see both Thread and Event in the stack trace, and each of those have some structures that need to be set up.
I recommend calling qcc::Init() and qcc::Shutdown(). From: [email protected] [mailto:[email protected]] On Behalf Of Ry Jones Sent: Friday, June 17, 2016 5:05 PM To: Thorsten Alteholz <[email protected]> Cc: Allseen Core <[email protected]> Subject: Re: [Allseen-core] Segmentation fault if you have a solid repro for that, could you file a bug with the code? jira.allseenalliance.org<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fjira.allseenalliance.org&data=01%7c01%7ckkane%40microsoft.com%7c9f2cfe1e6a3b4c879c2508d3970c420a%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=V8TN0DrkntbHgzxm%2bOLJJsMhxjipva4jUBpTQYHeUVY%3d> On Fri, Jun 17, 2016 at 1:58 PM, Thorsten Alteholz <[email protected]<mailto:[email protected]>> wrote: Hi, while playing a bit with ProducerService from the base services, I stumbled upon the following segmentation fault: Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7ab08a0 in std::_Rb_tree<qcc::String const, std::pair<qcc::String const, unsigned int>, std::_Select1st<std::pair<qcc::String const, unsigned int> >, std::less<qcc::String const>, std::allocator<std::pair<qcc::String const, unsigned int> > >::_M_begin (this=0x58) at /usr/include/c++/5/bits/stl_tree.h:652 652 { return static_cast<_Link_type>(this->_M_impl._M_header._M_parent); } (gdb) bt #0 0x00007ffff7ab08a0 in std::_Rb_tree<qcc::String const, std::pair<qcc::String const, unsigned int>, std::_Select1st<std::pair<qcc::String const, unsigned int> >, std::less<qcc::String const>, std::allocator<std::pair<qcc::String const, unsigned int> > >::_M_begin (this=0x58) at /usr/include/c++/5/bits/stl_tree.h:652 #1 0x00007ffff7ab0ba6 in std::_Rb_tree<qcc::String const, std::pair<qcc::String const, unsigned int>, std::_Select1st<std::pair<qcc::String const, unsigned int> >, std::less<qcc::String const>, std::allocator<std::pair<qcc::String const, unsigned int> > >::find (this=0x58, __k=...) at /usr/include/c++/5/bits/stl_tree.h:2295 #2 0x00007ffff7ab0719 in std::map<qcc::String const, unsigned int, std::less<qcc::String const>, std::allocator<std::pair<qcc::String const, unsigned int> > >::find (this=0x58, __x=...) at /usr/include/c++/5/bits/stl_map.h:846 #3 0x00007ffff7aaf1c0 in qcc::DebugControl::Check (this=0x0, type=DBG_API_TRACE, module=0x7ffff7bce9f9 "EVENT") at common/src/Debug.cc:193 #4 0x00007ffff7aafd3a in _QCC_DbgPrintCheck (type=DBG_API_TRACE, module=0x7ffff7bce9f9 "EVENT") at common/src/Debug.cc:460 #5 0x00007ffff7b76dec in CreateMechanism (readFd=0x55555580b188, writeFd=0x55555580b18c) at common/os/posix/Event.cc:653 #6 0x00007ffff7b77111 in qcc::Event::Event (this=0x55555580b188) at common/os/posix/Event.cc:731 #7 0x00007ffff7ab7d35 in qcc::Thread::Thread (this=0x55555580b180, name=..., func=0x0, isExternal=false) at common/os/posix/Thread.cc:189 #8 0x000055555557a56d in ?? () #9 0x00000000000025e8 in ?? () #10 0x0000555555574be0 in ?? () #11 0x00007ffff7dd6e88 in vtable for qcc::String () from /usr/lib/x86_64-linux-gnu/liballjoyn_about.so.1504 #12 0x000055555580d770 in ?? () #13 0x0000000000000000 in ?? () (gdb) I only built the core libraries as debug version, so some traces in the higher numbers are missing. At least I can say that DebugControl::Init() was done. Sometimes I also see a segmenation fault in DebugControl::AddTagLevelPair() when a new pair should be added to modLevels. Do those errors ring any bell? Thorsten _______________________________________________ Allseen-core mailing list [email protected]<mailto:[email protected]> https://lists.allseenalliance.org/mailman/listinfo/allseen-core<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2flists.allseenalliance.org%2fmailman%2flistinfo%2fallseen-core&data=01%7c01%7ckkane%40microsoft.com%7c9f2cfe1e6a3b4c879c2508d3970c420a%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=a5HxBxDS%2bn0kVOXlQ3%2fnCNAtfjOdmDK6GhyVynFtjcs%3d>
_______________________________________________ Allseen-core mailing list [email protected] https://lists.allseenalliance.org/mailman/listinfo/allseen-core
