|
From: Philippe W. <phi...@sk...> - 2023-04-16 12:36:01
|
On Sun, 2023-04-16 at 02:28 +0200, Mark Wielaard wrote: > > The problem is solved by giving an absolute path for the remote exec-file: > > (gdb) set remote exec-file /home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers > > It doesn't need to be an absolute path, it can also be a relative path > like: set remote exec-file ./sleepers > > Note that this is similar to how valgrind normally resolves > executables. Effectively. I was confused as GDB does not use the PATH. E.G.: philippe@md:gdbserver_tests$ valgrind -q sleepers valgrind: sleepers: command not found philippe@md:gdbserver_tests$ gdb -q sleepers Loaded DUEL.py 0.9.6, high level data exploration language Reading symbols from sleepers... (gdb) start Temporary breakpoint 1 at 0x16fc: file sleepers.c, line 138. So, it looks like in multi mode, I put my brain in "GDB mode". where absolute (or relative path) is not needed :). > > > > Not too sure what is going wrong/what I am doing wrong ... > > Nothing. There is something about sleepers that causes this. It also > happens for me. I'll try to debug it. But it works when you give vgdb > -d -d debug options... Humph, race condition/timing related bugs are hard to debug :(. Thanks Philippe |