aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Object/ObjectFile.cpp
diff options
context:
space:
mode:
authorTodd Fiala <tfiala@google.com>2014-01-21 18:46:22 +0000
committerTodd Fiala <tfiala@google.com>2014-01-21 18:46:22 +0000
commit4bd862206a2d7beba9ae5564f835644f7ea62c47 (patch)
tree110a4568bf9e11d52f25f9317d66d78ec3604f19 /llvm/lib/Object/ObjectFile.cpp
parent3eff225a444c2ebb170b7d39e73e469f0961392b (diff)
downloadllvm-4bd862206a2d7beba9ae5564f835644f7ea62c47.zip
llvm-4bd862206a2d7beba9ae5564f835644f7ea62c47.tar.gz
llvm-4bd862206a2d7beba9ae5564f835644f7ea62c47.tar.bz2
Add --lldb-command command-line option to lldb-gdbserver
lldb-gdbserver now takes zero or more --lldb-command {command} options that get executed by the command interpreter prior to starting up a child debuggee process. The short form is -c {command}. This is similar to how lldb-platform works. This command can be used to enable logging in more than just the gdb-remote log channel. Here is an example startup sequence that allows logging of lldb host and process log categories to one file and gdb-remote packets to another file: lldb-gdbserver -c 'log enable -f lgs.log lldb process host' \ -c 'log enable -f lgs_packets.log gdb-remote packets' \ localhost:5432 ./some_exe llvm-svn: 199761
Diffstat (limited to 'llvm/lib/Object/ObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions