Reverse Engineering Stack Exchange is a question and answer site for researchers and developers who explore the principles of a system through analysis of its structure, function, and operation. It only takes a minute to sign up.
Sign up to join this community
I run gdbserver
gdbserver --attach :<port> <pid> and then connect with gdb-multiarch
The problem is that until I connect with gdb-multiarch and run c the process is stop.
Can I continue the process after I attach with gdbserver inside hte machine that run gdbserver ?
The main built-in way I see to do this is to use gdbserver --multi without attaching to a process at that time. Then, you connect with target extended-remote in gdb, and then run the attach <pid> in gdb.
You could also instead use a wrapper on the debugee to not start gdbserver until a connection is made:
$ socat tcp-l:<port>,reuseaddr,fork exec:"gdbserver --once --attach <pid>"
Statically compiled builds of socat can be made by you or often found online.
gdb-multiarch will connet