[lldb-dev] Fixing TestSettings.py for remote targets

[Vince Harron]

Hi all,

settings set target.error-path stderr.txt automatically resolves stderr.txt
to the local file system.

(lldb) settings set target.error-path stderr.txt
(lldb) settings show target.error-path
target.error-path (file) =
"/usr/local/google/home/vharron/ll/tot/lldb/test/stderr.txt"

This doesn't make any sense for remote targets

(lldb) platform select remote-linux
(lldb) platform connect connect://192.168.100.132:5432
(lldb) platform settings --working-dir /tmp
(lldb) settings set target.error-path stderr.txt
(lldb) settings show target.error-path
target.error-path (file) =
"/usr/local/google/home/vharron/ll/tot/lldb/test/stderr.txt"

I propose that we don't resolve target.error-path or target.output-path but
leave it as-is and let the platform interpret it.  This probably means the
file will be created relative to the working directory of the remote
process.

When you call "settings show target.error-path" it will just return the
original error string passed to "settings set target.error-path"  (e.g.
I'll change it from OptionValueFileSpec to OptionValueString.)

Thoughts?

Vince

Vince Harron | Technical Lead Manager | vharron at google.com | 858-442-0868
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20150213/a560f300/attachment.html>