search for: linfo_string7

Displaying 6 results from an estimated 6 matches for "linfo_string7".

Did you mean: linfo_string
2015 Sep 18
5
Fwd: Skipping names of temporary symbols increased size of ARM binaries.
...r names. Its bfd_is_local_label_name function returns false and the labels are not skipped. Before r236642 the names were inserted into object files: readelf -s main.o Num: Value Size Type Bind Vis Ndx Name 23: 0000007a 0 NOTYPE LOCAL DEFAULT 9 .Linfo_string7 bfd_is_local_label_name returns true if the name starts with ".L" and the symbol is skipped. This is not critical for small projects but can create noticeable overhead for the big ones. Any help will be much appreciated. Thank you. Oleg -------------- next part -------------- An HTML a...
2014 Feb 19
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...# Abbrev [5] 0x7f:0x7 DW_TAG_base_type > .int Linfo_string4 # DW_AT_name > .byte 5 # DW_AT_encoding > .byte 4 # DW_AT_byte_size > .byte 5 # Abbrev [5] 0x86:0x7 DW_TAG_base_type > .int Linfo_string7 # DW_AT_name > .byte 6 # DW_AT_encoding > .byte 1 # DW_AT_byte_size > .byte 6 # Abbrev [6] 0x8d:0x5 DW_TAG_pointer_type > .int 134 # DW_AT_type > .byte 6 # Abbrev [...
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
2020 Jun 22
3
Hardware ASan Generating Unknown Instruction
Hi, I am trying to execute a simple hello world program compiled like so: path/to/compiled/clang -o test --target=aarch64-linux-gnu -march=armv8.5-a -fsanitize=hwaddress --sysroot=/usr/aarch64-linux-gnu/ -L/usr/lib/gcc/aarch64-linux-gnu/10.1.0/ -g test.c However, when I look at the disassembly, there is an unknown instruction listed at 0x2d51c: 000000000002d4c0 main: 2d4c0: ff c3 00 d1
2014 Feb 20
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...; .int Linfo_string4 # DW_AT_name > > .byte 5 # DW_AT_encoding > > .byte 4 # DW_AT_byte_size > > .byte 5 # Abbrev [5] 0x86:0x7 > DW_TAG_base_type > > .int Linfo_string7 # DW_AT_name > > .byte 6 # DW_AT_encoding > > .byte 1 # DW_AT_byte_size > > .byte 6 # Abbrev [6] 0x8d:0x5 > DW_TAG_pointer_type > > .int 134 #...