search for: dw_form_flag_present

Displaying 20 results from an estimated 28 matches for "dw_form_flag_present".

2017 Apr 04
2
GDB doesn't work with IR-originated debug info
...(0x000002b4) DW_AT_frame_base [DW_FORM_exprloc] (<0x1> 54 ) DW_AT_name [DW_FORM_strp] ( .debug_str[0x00001616] = "FB_FPUMP at HORIZONTAL") DW_AT_type [DW_FORM_ref_addr] (*0x000000006e440296*) DW_ AT_external [DW_FORM_flag_present] (true) In the original object file the corresponding record was: 0x00000296: DW_TAG_base_type [10] DW_AT_name [DW_FORM_strp] ( .debug_str[0x0000068f] = "void") DW_AT_encoding [DW_FORM_data1] (0x00) DW_AT_byte_size [DW_FORM_dat...
2014 Feb 19
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...t; .byte 58 # DW_AT_decl_file > .byte 11 # DW_FORM_data1 > .byte 59 # DW_AT_decl_line > .byte 11 # DW_FORM_data1 > .byte 39 # DW_AT_prototyped > .byte 25 # DW_FORM_flag_present > .byte 73 # DW_AT_type > .byte 19 # DW_FORM_ref4 > .byte 63 # DW_AT_external > .byte 25 # DW_FORM_flag_present > .byte 17 # DW_AT_low_pc > .byte 1 # D...
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
2018 Mar 23
2
Question about debug information for global variables
...;> With deref: >> 0x00000032: DW_TAG_variable [2] >> DW_AT_name [DW_FORM_strp] ( >> .debug_str[0x0000001d] = "var1") >> DW_AT_type [DW_FORM_ref4] (cu + 0x0049 => {0x00000049}) >> DW_AT_external [DW_FORM_flag_present] (true) >> DW_AT_location [DW_FORM_exprloc] (<0xd> 03 b0 >> 2e 00 00 00 00 00 00 06 10 00 22 ) >> >> >> Without deref: >> 0x00000032: DW_TAG_variable [2] >> DW_AT_name [DW_FORM_strp] ( >> .debug_str...
2018 Mar 22
2
Question about debug information for global variables
...e.o The DW_AT_location values are different: With deref: 0x00000032: DW_TAG_variable [2] DW_AT_name [DW_FORM_strp] ( .debug_str[0x0000001d] = "var1") DW_AT_type [DW_FORM_ref4] (cu + 0x0049 => {0x00000049}) DW_AT_external [DW_FORM_flag_present] (true) DW_AT_location [DW_FORM_exprloc] (<0xd> 03 b0 2e 00 00 00 00 00 00 06 10 00 22 ) Without deref: 0x00000032: DW_TAG_variable [2] DW_AT_name [DW_FORM_strp] ( .debug_str[0x0000001d] = "var1") DW_AT_type [DW_FORM...
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
2018 Mar 23
0
Question about debug information for global variables
...t;>> 0x00000032: DW_TAG_variable [2] >>> DW_AT_name [DW_FORM_strp] ( >>> .debug_str[0x0000001d] = "var1") >>> DW_AT_type [DW_FORM_ref4] (cu + 0x0049 => {0x00000049}) >>> DW_AT_external [DW_FORM_flag_present] (true) >>> DW_AT_location [DW_FORM_exprloc] (<0xd> 03 b0 >>> 2e 00 00 00 00 00 00 06 10 00 22 ) >>> >>> >>> Without deref: >>> 0x00000032: DW_TAG_variable [2] >>> DW_AT_name [DW_FORM_strp]...
2018 Mar 22
0
Question about debug information for global variables
...are different: > > With deref: > 0x00000032: DW_TAG_variable [2] > DW_AT_name [DW_FORM_strp] ( > .debug_str[0x0000001d] = "var1") > DW_AT_type [DW_FORM_ref4] (cu + 0x0049 => {0x00000049}) > DW_AT_external [DW_FORM_flag_present] (true) > DW_AT_location [DW_FORM_exprloc] (<0xd> 03 b0 > 2e 00 00 00 00 00 00 06 10 00 22 ) > > > Without deref: > 0x00000032: DW_TAG_variable [2] > DW_AT_name [DW_FORM_strp] ( > .debug_str[0x0000001d] = "var1&quot...
2012 Oct 18
0
[LLVMdev] DWARF 2/3 backwards compatibility?
...o Dwarf 5, and the next GDB. The framework is a set of GCC like gdwarf[2,3,4,5] flags. I can see cases where compatibility is 2,3 or 2,3,4, so maybe the flag is a number to allow <=3 tests, have to sleep on that. This flag must go to the backend. Then the patch will change the conditional for DW_FORM_flag_present that caused the problem back to the old DW_FORM_flag when -gdwarf2 or 3 is set. In the future, there is a now a place to address compatibility issues that come up. ---- Monitoring this with GDB Testsuite as Jenkins or Buildbot would be a good idea. 20K+ tests are difficult to duplicate. GDB Te...
2015 Nov 13
2
[PATCH] D14358: DWARF's forward decl of a template should have template parameters.
..._FORM_ref4 0x00000054 > +-00000054 DW_TAG_pointer_type > +-DW_AT_type DW_FORM_ref4 0x00000059 > +-00000059 DW_TAG_class_type "A<MONKEY>" > -DW_AT_name DW_FORM_strp "A<MONKEY>" > -DW_AT_declaration DW_FORM_flag_present > > +-00000073 DW_TAG_structure_type "C" > -DW_AT_name DW_FORM_strp "C" > +-0000007b DW_TAG_member "p" > -DW_AT_name DW_FORM_strp "p" > +-DW_AT_type DW_FORM_ref4 0x00000088 > +-00000088 DW_TAG_pointer_type >...
2012 Oct 18
6
[LLVMdev] DWARF 2/3 backwards compatibility?
Rick Foos wrote: > The error we are getting is: > “Undefined Form Value: 25” > ... > DW_FORM_flag_present caused the problem. The old DW_FORM_flag works for us. I see this error from GDB 7.0 but GDB 7.2 is okay with it. Now you know as much as I do. :-) Eric Christopher wrote: > [in reply to what Renato Golin wrote:] > > With time, you might get to a point where Dwarf is a first-class >...
2015 Dec 09
2
[PATCH] D14358: DWARF's forward decl of a template should have template parameters.
..._FORM_ref4 0x00000054 > +-00000054 DW_TAG_pointer_type > +-DW_AT_type DW_FORM_ref4 0x00000059 > +-00000059 DW_TAG_class_type "A<MONKEY>" > -DW_AT_name DW_FORM_strp "A<MONKEY>" > -DW_AT_declaration DW_FORM_flag_present > > +-00000073 DW_TAG_structure_type "C" > -DW_AT_name DW_FORM_strp "C" > +-0000007b DW_TAG_member "p" > -DW_AT_name DW_FORM_strp "p" > +-DW_AT_type DW_FORM_ref4 0x00000088 > +-00000088 DW_TAG_pointer_type >...
2015 Dec 09
2
[PATCH] D14358: DWARF's forward decl of a template should have template parameters.
..._FORM_ref4 0x00000054 > +-00000054 DW_TAG_pointer_type > +-DW_AT_type DW_FORM_ref4 0x00000059 > +-00000059 DW_TAG_class_type "A<MONKEY>" > -DW_AT_name DW_FORM_strp "A<MONKEY>" > -DW_AT_declaration DW_FORM_flag_present > > +-00000073 DW_TAG_structure_type "C" > -DW_AT_name DW_FORM_strp "C" > +-0000007b DW_TAG_member "p" > -DW_AT_name DW_FORM_strp "p" > +-DW_AT_type DW_FORM_ref4 0x00000088 > +-00000088 DW_TAG_pointer_type >...
2016 Dec 15
1
distinct DISubprograms hindering sharing inlined subprogram descriptions
On Thu, Dec 15, 2016 at 11:35 AM Mehdi Amini <mehdi.amini at apple.com> wrote: > > > On Dec 15, 2016, at 10:54 AM, David Blaikie via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > Branching off from a discussion of improvements to DIGlobalVariable > representations that Adrian's working on - got me thinking about related > changes that have
2018 Mar 22
0
Question about debug information for global variables
> On Mar 22, 2018, at 4:08 PM, Roman Levenstein <romixlev at gmail.com> wrote: > > Hi, > > I'm trying to achieve the following: > > - I have a global variable BaseAddress that holds the base address of > a contiguous dynamically allocated memory block. > > - I have a number of logical variables of different types that are > mapped on certain address
2015 Dec 09
2
[PATCH] D14358: DWARF's forward decl of a template should have template parameters.
..._FORM_ref4 0x00000054 > +-00000054 DW_TAG_pointer_type > +-DW_AT_type DW_FORM_ref4 0x00000059 > +-00000059 DW_TAG_class_type "A<MONKEY>" > -DW_AT_name DW_FORM_strp "A<MONKEY>" > -DW_AT_declaration DW_FORM_flag_present > > +-00000073 DW_TAG_structure_type "C" > -DW_AT_name DW_FORM_strp "C" > +-0000007b DW_TAG_member "p" > -DW_AT_name DW_FORM_strp "p" > +-DW_AT_type DW_FORM_ref4 0x00000088 > +-00000088 DW_TAG_pointer_type >...
2016 Oct 07
0
Wine release 1.8.5
...lacks support for level 8, global default printer settings) 31693 CAPCOM games using gamepad start with axes X/Y pressed up/left 31913 EasyPal version August 6 2012 crashes on unimplemented function msvcp60.dll.??Dstd@@YA?AV?$complex at N@0 at ABNABV10@@Z 32491 dbghelp doesn't support DW_FORM_flag_present 32936 SmartMusic 2012/2014 crashes on startup (Core Audio adapter 'PKEY_DeviceInterface_FriendlyName' property not supported) 33140 Photos opened in Nikon Capture NX 2.4 have inverted red and blue channel for displaying. 33398 Word / Excel 2010: crash when clicked (2nd or 3rd times...
2018 Mar 22
2
Question about debug information for global variables
Hi, I'm trying to achieve the following: - I have a global variable BaseAddress that holds the base address of a contiguous dynamically allocated memory block. - I have a number of logical variables of different types that are mapped on certain address ranges inside the memory block pointed to by BaseAddress. The offset and the size of each such logical variable inside the memory block are
2012 Oct 17
0
[LLVMdev] DWARF 2/3 backwards compatibility?
> My GDB Testsuite runs have been failing more tests, and now an internal test > has started failing on some missing dwarf 3 records. What is the error message or the nature of the failures you are seeing ? Pranav Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
2012 Oct 17
2
[LLVMdev] DWARF 2/3 backwards compatibility?
My GDB Testsuite runs have been failing more tests, and now an internal test has started failing on some missing dwarf 3 records. Changing compile flags to emit dwarf 2 didn't help. In the past there has been some effort to pass GDB Testsuite, including Dwarf 2 backwards compatibility. What is the plan/mechanism for maintaining Dwarf 2/3 compatibility? -- Rick Foos Qualcomm Innovation