[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 #20 from Pedro Alves <pedro at palves dot net> ---
> If it implemented vFile you could use "target remote | ssh mumble valgrind"

Yeah.

> The main thing is we have to document the procedure somehow.

If we rely on vFile without any obfuscation, it becomes all GDB implementation
detail, because it's just:

GDB does target_fileio_open("target:/etc/machine-id") + target_fileio_read, and
compares contents with its own /etc/machine-id.

Very similar to the /tmp/ idea.

The /tmp idea would work on Windows too, I think.

Maybe we could also try target_fileio_stat("target:/path/to/valgrind") and
compare to 
stat("/path/to/valgrind")

Maybe we could even do both, try /etc/machine-id, and fallback to /tmp.  And
then to stat.  And whatever other file-based fingerprinting method we come up
with to try to rule out partially-shared filesystems.

If we need obfuscation, then we could I guess add a new
TARGET_OBJECT_MACHINE_ID, and qXfer:read:machine-id packet to go along with it,
and document what that means for the different OSs.

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