[llvm-bugs] [Bug 33663] New: clang doesn't emit debugging information when compiling assembly files directly to an executable
via llvm-bugs
llvm-bugs at lists.llvm.org
Fri Jun 30 10:54:30 PDT 2017
https://bugs.llvm.org/show_bug.cgi?id=33663
Bug ID: 33663
Summary: clang doesn't emit debugging information when
compiling assembly files directly to an executable
Product: new-bugs
Version: 4.0
Hardware: Macintosh
OS: MacOS X
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedbugs at nondot.org
Reporter: mike.benfield at gmail.com
CC: llvm-bugs at lists.llvm.org
If I compile an assembly file (with -g) to an object file, then link the object
file, debugging works correctly. But if I compile an assembly file (with -g)
directly to an executable, it apparently doesn't have debugging information.
Since this is different behavior than when clang compiles C language files, I
believe this is a bug. Example:
$ cat trash.s
.intel_syntax noprefix
.text
.global _main
_main:
mov rax, 5
ret
$ clang -g trash.s
$ lldb a.out
(lldb) target create "a.out"
Current executable set to 'a.out' (x86_64).
(lldb) breakpoint set -f trash.s -l 6
Breakpoint 1: no locations (pending).
WARNING: Unable to resolve breakpoint to any actual locations.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20170630/2106cc0b/attachment.html>
More information about the llvm-bugs
mailing list