summaryrefslogtreecommitdiffstats
path: root/clang/lib/CodeGen/CodeGenModule.h
diff options
context:
space:
mode:
authorJonas Devlieghere <jonas@devlieghere.com>2019-11-07 11:13:47 -0800
committerJonas Devlieghere <jonas@devlieghere.com>2019-11-07 12:43:59 -0800
commitc62a9f180c26e2fed012531caa581f0d736bfed9 (patch)
tree928eb99afbf2384493216a45cb0a78a8fdfa05ad /clang/lib/CodeGen/CodeGenModule.h
parent96119586c9968f3c1e56513d52956f5738cf4d26 (diff)
downloadbcm5719-llvm-c62a9f180c26e2fed012531caa581f0d736bfed9.tar.gz
bcm5719-llvm-c62a9f180c26e2fed012531caa581f0d736bfed9.zip
[lldb] Improve assert in GDBRemoteCommunicationReplayServer
While investigating an issue where a different packet was sent during replay I noticed how annoying it is that the existing assert doesn't specify what packet is actually different. It's printed to the log, but enabling logging has the potential to change LLDB's behavior. The same is true when debugging LLDB while it's replaying the reproducer. I replaced the assert with a printf of the unexpected packet followed by a fatal_error wrapped in ifndef NDEBUG. The behavior is the same as the previous assert, just with more/better context.
Diffstat (limited to 'clang/lib/CodeGen/CodeGenModule.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud