CODEWITHSUNDEEP
cdebugginggdbvalgrind
highsciguy
highsciguy

Reputation: 2647

GDB remote debugging with valgrind

If I remote debug using gdb I connect to the gdbserver using

target remote host:2345

If I debug memory errors with valgrind and gdb (to break on invalid memory access) I use

target remote | vgdb

(after starting 

valgrind --track-origins=yes --vgdb=yes --vgdb-error=0 [binary]

on the local machine)

Can I combine the two to debug memory errors on a remote machine?

Note that I want to avoid using a login shell on the remote machine to work there.

Upvotes: 6

Views: 7284

Answers (1)

Employed Russian
Employed Russian

Reputation: 213957

Can I combine the two to debug memory errors on a remote machine?

Yes: current vgdb accepts --port= argument since this commit:

r12204 | sewardj | 2011-10-22 13:38:08 -0700 (Sat, 22 Oct 2011) | 5 lines

So run vgdb --port=2345, and then (gdb) target remote host:2345 as usual.

Upvotes: 7

Related Questions