Rasnet server fails when attached to GDB

[Veranika Liaukevich]

During the development process, it is useful to be able to attach to the rasserver process with GDB for debugging. However, if rasdaman uses rasnet protocol, the server process shortly fails:

$ sudo gdb -p $(pgrep rasserver)
....
(gdb) b QtVariable::evaluate
Breakpoint 1 at 0x4c4aca
(gdb) c
Continuing.
...
(gdb) b qtvariable.cc:209
Breakpoint 1 at 0x6a76b8: file qtvariable.cc, line 209.
(gdb) c
Continuing.
[Switching to Thread 0x7fecc5d5d700 (LWP 11795)]

Breakpoint 1, QtVariable::evaluate (this=0x7fecb8014560, inputList=0x7fecb80138f0) at qtvariable.cc:209
209	            int pos = 0;
(gdb) n
211	            for( QtDataList::iterator iter=inputList->begin(); iter!=inputList->end() && !dataObject; iter++ )
(gdb) n

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fecc6f69700 (LWP 11793)]
0x00007fecd6d61cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56	../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) n
[Thread 0x7fecc976e700 (LWP 11785) exited]
[Thread 0x7fecca770700 (LWP 11783) exited]
[Thread 0x7fecc9f6f700 (LWP 11784) exited]
[Thread 0x7fecc8f6d700 (LWP 11786) exited]
[Thread 0x7fecc876c700 (LWP 11787) exited]
[Thread 0x7fecc776a700 (LWP 11792) exited]
[Thread 0x7fecc6f69700 (LWP 11793) exited]
[Thread 0x7fecc655e700 (LWP 11794) exited]
[Thread 0x7fecc5d5d700 (LWP 11795) exited]
[Thread 0x7fecda813780 (LWP 11780) exited]

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.

[Dimitar Misev]

I couldn't reproduce, attaching gdb works fine.