Can't debug rasserver with gdb

[Dimitar Misev]

It seems like gdb just doesn't work anymore with rasnet (setting breakpoints or doing anything else). Can you check as well? Any ideas?

ps aux | grep rasserver # to find the pid
gdb -p <pid>

[Alex Toader]

In rasnet, the server process is terminated if it does not respond to status checks from rasmgr. You can bypass this by modifying:
SERVER_MANAGER_CLEANUP_INTERVAL
and
CLIENT_MANAGER_CLEANUP_INTERVAL
in rasmgr_x/constants.hh to large values.

Ideally, we should work towards having the server functionality covered by unit tests to make debugging easier.

[Dimitar Misev]

Being able to attach to rasserver with gdb is essential.

[Peter Baumann]

wasn't directql meant for purposes like testing on QL level?

[Dimitar Misev]

Yes in this case I resorted to directql, but if it was some issue with the protocol then that wouldn't work and the way to enable it is a bit cumbersome.

Maybe we can put this stuff in some developers guide:

In rasnet, the server process is terminated if it does not respond to status checks from rasmgr. > You can bypass this by modifying:
SERVER_MANAGER_CLEANUP_INTERVAL
and
CLIENT_MANAGER_CLEANUP_INTERVAL
in rasmgr_x/constants.hh to large values.

[Alex Toader]

You can attach gdb to the server process without any problem. You just have to make sure that rasmgr does not kill the server process while you are debugging (by setting the above variables).
@Dimitar, where should I put the above information?

[Dimitar Misev]

I think this would be a fitting place: wiki:DebuggingBenchmarking

[Dimitar Misev]

Added at wiki:DebuggingBenchmarking#Debugingrasserver