Unable to debug exasock application using gdb. about exanic-software HOT 5 OPEN

An alternative method is to invoke gdb as normal and then set the exec-wrapper:

(gdb) set exec-wrapper env LD_PRELOAD=/usr/local/lib/exasock/libexasock_preload.so

or for debug/trace:

(gdb) set exec-wrapper env LD_PRELOAD=/usr/local/lib/exasock/libexasock_preload_debug.so export EXASOCK_TRACE=1

There are other parameters in the /usr/local/bin/exasock wrapper script though the exasock wrapper and libs might be installed somewhere else on your system.

from exanic-software.

You should be able to preload the exasock library before invoking gdb with something similar to the following:

exasock gdb --args application executable with parameter list

Also, for additional debugging the exasock library/system calls, can use the following:

exasock --trace --debug gdb --args application executable with parameter list

from exanic-software.

I'm also unable to use gdb with exasock.
If I run exasock --debug gdb --args <myprogram> <my program arguments> the gdb will stuck at Starting program: ... after typing the command run.

from exanic-software.

I have the same issue Starting program: ... after typing the command run. Even the example.

from exanic-software.

An alternative method is to invoke gdb as normal and then set the exec-wrapper:

(gdb) set exec-wrapper env LD_PRELOAD=/usr/local/lib/exasock/libexasock_preload.so

or for debug/trace:

(gdb) set exec-wrapper env LD_PRELOAD=/usr/local/lib/exasock/libexasock_preload_debug.so export EXASOCK_TRACE=1

There are other parameters in the /usr/local/bin/exasock wrapper script though the exasock wrapper and libs might be installed somewhere else on your system.

That works for me. Thanks!

from exanic-software.