summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp
diff options
context:
space:
mode:
authorDuncan P. N. Exon Smith <dexonsmith@apple.com>2015-02-25 22:08:21 +0000
committerDuncan P. N. Exon Smith <dexonsmith@apple.com>2015-02-25 22:08:21 +0000
commit89c1eaa5317ad5abea69e973d2485ca1ab790975 (patch)
tree96dc23f7335d08b32e6429de74cccf0698b9885f /lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp
parentac10b0d61da71ff72fe167e6e29f0dd2e8043131 (diff)
downloadbcm5719-llvm-89c1eaa5317ad5abea69e973d2485ca1ab790975.tar.gz
bcm5719-llvm-89c1eaa5317ad5abea69e973d2485ca1ab790975.zip
IR: Annotate dump methods with LLVM_DUMP_METHOD
It turns out we have a macro to ensure that debuggers can access `dump()` methods. Use it. Hopefully this will prevent me (and others) from committing crimes like in r223802 (search for /10000/, or just see the fix in r224407). llvm-svn: 230555
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud