[Bug gdb/30541] Add target valgrind

["pedro at palves dot net" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=30541

--- Comment #30 from Pedro Alves <pedro at palves dot net> ---
> Using Q* to set the environment and the working directory seems
> clearly better to me, and in fact the only way it can work
> properly.  The problem case is something like:
>
> (gdb) set env X y
> (gdb) start
> (gdb) add-inferior blah blah
> (gdb) set env X z
> (gdb) start

GDB only sends the env vars that were set/cleared with "set/unset env".  It
does not send the whole environment that GDB has.  Same for the working
directory.  If you user hasn't done "set cwd" explicitly, then GDB will tell
the server to use its default cwd.

That's why I was suggesting to just start vgdb with the environment you want,
like if done by "target valgrind", then it would already inherit gdb's
environment.  If started via "ssh server vgdb", then it wouldn't make sense to
send the whole of gdb's environment.  So that's why I was asking what would be
the use case, if users aren't ideally going to start vgdb themselves.

-- 
You are receiving this mail because:
You are on the CC list for the bug.