This patch allows LLDB to print column info in backtraces et al. if available, which is useful when the backtrace contains a frame like the following:
f(can_crash(0), can_crash(1));
Paths
| Differential D51661
Print column info in backtraces et al. if available ClosedPublic Authored by aprantl on Sep 4 2018, 3:49 PM.
Details Summary This patch allows LLDB to print column info in backtraces et al. if available, which is useful when the backtrace contains a frame like the following: f(can_crash(0), can_crash(1));
Diff Detail Event TimelineComment Actions We shouldn't have the colon character be part of the ${line.column} formatting itself. See inlined comments.
This revision now requires changes to proceed.Sep 5 2018, 9:42 AM
Comment Actions See my inlined comments about returning true and false correctly for the column and the correction to the format string
Comment Actions Address review feedback. Thanks you, I was wondering how to properly implement an optional element! This revision is now accepted and ready to land.Sep 5 2018, 4:46 PM Closed by commit rL341506: Print column info in backtraces et al. if available (authored by adrian). · Explain WhySep 5 2018, 4:54 PM This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 164104 include/lldb/Core/FormatEntity.h
packages/Python/lldbsuite/test/functionalities/asan/Makefile
packages/Python/lldbsuite/test/functionalities/asan/TestReportData.py
source/Core/Debugger.cpp
source/Core/FormatEntity.cpp
|
Add the colon between the ${line.number} and ${line.column} here, not as part of the "${line.column}" formatting itself.