diff options
| author | David Blaikie <dblaikie@gmail.com> | 2016-05-26 00:22:26 +0000 |
|---|---|---|
| committer | David Blaikie <dblaikie@gmail.com> | 2016-05-26 00:22:26 +0000 |
| commit | 2274808153e8d3ee749521b5d6e56d8cf4c8c4f7 (patch) | |
| tree | 72624fdca633434bd040e3be61fca9778d9cde12 /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStopAndContinue.py | |
| parent | a099268e8595f9df0f1b38688e19c70665c377a1 (diff) | |
| download | bcm5719-llvm-2274808153e8d3ee749521b5d6e56d8cf4c8c4f7.tar.gz bcm5719-llvm-2274808153e8d3ee749521b5d6e56d8cf4c8c4f7.zip | |
PR11740: Disable assembly debug info when assembly already contains line directives
If there is already debug info in the assembly file, and user hope to
use -g option for compiling, we think we should not directly report an
error.
According to what GNU assembler did, it just reused the debug info in
the assembly file, and turned off the DEBUG_TYPE option so that there
will be no new debug info emitted by assembler. This fix is just as what
GNU assembler did.
The concern is the situation that there are two .text sections in the
assembly file, one with debug info and the other one without. Currently
with this fix, the assembler will no longer generate any debug info for
the second .text section. And this is what GNU assembler exactly did for
this situation. So I think this still make some sense.
Patch by Zhizhou Yang!
Differential Revision: http://reviews.llvm.org/D20002
llvm-svn: 270806
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStopAndContinue.py')
0 files changed, 0 insertions, 0 deletions
