Displaying 6 results from an estimated 6 matches for "linfo_string8".
Did you mean:
linfo_string
2017 May 03
2
clang assembler keeps .Linfo_string symbols?
On 3 May 2017 at 08:01, Rafael Avila de Espindola via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Can you provide a .s file that shows the difference?
I managed to reproduce it by compiling 'char *var = "whatever";' in
debug mode (so clang -target arm-none-eabi tmp.c -g"). Direct compile
leaves no assembler-local strings, but for some reason going via -S
does.
2017 May 03
2
clang assembler keeps .Linfo_string symbols?
...>> leaves no assembler-local strings, but for some reason going via -S
>> does. I've not investigated further I'm afraid.
> Sorry, had somehow replied off list:
>
> This reduces to
>
> .section .debug_str,"MS",%progbits,1
> .Linfo_string8:
> .long .Linfo_string8
>
> the difference comes from ELFObjectWriter::shouldRelocateWithSymbol. In
> particular
>
> // It looks like gold has a bug (http://sourceware.org/PR16794) and can
> // only handle section relocations to mergeable s...
2014 Feb 19
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...# DW_AT_decl_file
> .byte 2 # DW_AT_decl_line
> .int 146 # DW_AT_type
> .byte 2 # DW_AT_location
> .byte 145
> .byte 20
> .byte 4 # Abbrev [4] 0x54:0xe DW_TAG_variable
> .int Linfo_string8 # DW_AT_name
> .byte 1 # DW_AT_decl_file
> .byte 4 # DW_AT_decl_line
> .int 127 # DW_AT_type
> .byte 2 # DW_AT_location
> .byte 145
> .byte 16
> .byte 4 # A...
2014 Feb 18
1
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
All of this information is contained in the DWARF debug info that you must generate. Are you generating DWARF? If not, you will need to. If so, please attach an example program that contains DWARF and specify which function you are having trouble getting variable information for.
Greg Clayton
On Feb 18, 2014, at 12:44 AM, 杨勇勇 <triple.yang at gmail.com> wrote:
> Hi, all
>
> I
2014 Feb 18
4
[LLVMdev] How is variable info retrieved in debugging for executables generated by llvm backend?
Hi, all
I ported llvm backend and lldb recently. Both tools can basically work.
lldb is able to debug programs in asm style and frame unwinding is OK.
But "frame variable XX" does not work because lldb is not able to determine
the address of
XX from debug info.
Can someone give any clue?
Thanks in advance.
--
杨勇勇 (Yang Yong-Yong)
-------------- next part --------------
An HTML
2014 Feb 20
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...ine
> > .int 146 # DW_AT_type
> > .byte 2 # DW_AT_location
> > .byte 145
> > .byte 20
> > .byte 4 # Abbrev [4] 0x54:0xe
> DW_TAG_variable
> > .int Linfo_string8 # DW_AT_name
> > .byte 1 # DW_AT_decl_file
> > .byte 4 # DW_AT_decl_line
> > .int 127 # DW_AT_type
> > .byte 2 # DW_AT_location
> > .b...