summaryrefslogtreecommitdiffstats
path: root/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.h
diff options
context:
space:
mode:
authorTodd Fiala <todd.fiala@gmail.com>2014-10-09 00:11:43 +0000
committerTodd Fiala <todd.fiala@gmail.com>2014-10-09 00:11:43 +0000
commit952bccd2128ea8322358d99b22d9ccc936b0b7a6 (patch)
treee1a0cd99ef57028481b64d42358d36576ab3d5ff /llvm/lib/CodeGen/AsmPrinter/DwarfDebug.h
parent524002004db54bbc504c3286c6ee649ba441e2f4 (diff)
downloadbcm5719-llvm-952bccd2128ea8322358d99b22d9ccc936b0b7a6.tar.gz
bcm5719-llvm-952bccd2128ea8322358d99b22d9ccc936b0b7a6.zip
POSIX dynamic loader: add more logging around launch/attach, fix breakpoint handling on entry callback.
This change adds some logging around dynamic loader handling. It also fixes an issue where the dynamic loader entry breakpoint can end up being re-inserted, showing the wrong (i.e. software breakpoint) instruction at the stop location when a backtrace is displayed at program startup. I discussed with Jim Ingham a few weeks back. Essentially the one-hit breakpoints need to make it back to public state handling before the software breakpoint gets cleared. The flow I was hitting was that the breakpoint would get set, it would get hit, it would get cleared to step over, then it would get reapplied, when we never wanted it reapplied. Stops at the beginning of execution would then show backtraces with software breakpoint instructions in it, erroneously. This change fixes it. There might be a more elegant way to do this, or a flow change somewhere else to avoid, but it does fix an issue I experienced in startup breakpoint handling. llvm-svn: 219371
Diffstat (limited to 'llvm/lib/CodeGen/AsmPrinter/DwarfDebug.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud