#104 Segmentation fault when running hsolve

[Subhasis Ray]

Demos/traub_2005/py/test_tcr.py encounters segfault on executing moose.start() when setup with hsolve. When hsolve is not created it runs without any serious error.

[Subhasis Ray]

This segmenation fault occurs when trying to execute a message between KAHP_SLOWER (a Ca+2 dependent K+ channel) and CaPool (CaConc) for the first time. Possibly an issue with handling the custom messages?

Program received signal SIGSEGV, Segmentation fault.
0x00007fffe892b6fc in SingleMsg::exec (this=0x3c09ce0, q=0x7fffe7af5de0, arg=0x3cc4098, fid=46) at SingleMsg.cpp:40
(gdb) p e2_->getName()
$1001 = (const std::string &) @0x39d6b70: {static npos = <optimized out>, _M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0x248f078 "KAHP_SLOWER"}}
(gdb) p e1_->getName()
$1002 = (const std::string &) @0x39d4690: {static npos = <optimized out>, _M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0x25271f8 "CaPool"}}
(gdb) p arg[0]
$1003 = 0.00043412464184601094
(gdb) p fid
$1004 = 46

gdb backtrace:
#0 0x00007fffe892b6fc in SingleMsg::exec (this=0x3c09ce0, q=0x7fffe7af5de0, arg=0x3cc4098, fid=46) at SingleMsg.cpp:40
#1 0x00007fffe8d09486 in Element::exec (this=0x39d4690, qi=0x7fffe7af5de0, arg=0x3cc4098) at Element.cpp:357
#2 0x00007fffe8d0af6e in readBuf (buf=0x3cc1ac0, threadNum=1) at Qinfo.cpp:143
#3 0x00007fffe8d0afea in Qinfo::readQ (threadNum=1) at Qinfo.cpp:158
#4 0x00007fffe8961698 in processEventLoop (info=0x221a540) at ProcessLoop.cpp:66
#5 0x00007ffff7bc4d8c in start_thread (arg=0x7fffe7af6700) at pthread_create.c:304
#6 0x00007ffff6a89c2d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7 0x0000000000000000 in ?? ()

[Subhasis Ray]

This was more of a semantic issue: the prototype KAHP channel did not have the Mstring: 'addmsg1' element with the value 'cacon_path concOut . concen'

We need to find some way to handle such user errors.

[Subhasis Ray]

It was an issue with having the same finfos on ZombieHHChannel as in HHChannel. Now fixed in buildQ branch.