search for: at_typ

...age_name( .debug_str[0x000001c7] = "tart.reflect.Parameter.construct(tart.core.String)" ) > 0x000000d0: AT_decl_file( 0x3d ( "/Users/talin/Projects/tart/trunk/lib/std/tart/reflect/Parameter.tart" ) ) > 0x000000d1: AT_decl_line( 0x0d ( 13 ) ) > 0x000000d2: AT_type( cu + 0x00000066 => {0x00000103} ( ) ) > 0x000000d6: AT_external( 0x01 ) > 0x000000d7: AT_low_pc( 0x0000f780 ) > 0x000000db: AT_high_pc( 0x0000f7b1 ) > 0x000000df: AT_frame_base( <0x1> 55 ( reg5 ) ) > > 0x000000e1: NULL > > 0x000000e2: C...

...ful in this case. Here's what I get: - On OS X, with the "small" test cases I created, I get no errors at all. - On OS X, with my normal unit tests (with the standard library) I get hundreds of error messages of the following form: 0x00000882: DIE attribute 0x00000883: AT_type/FORM_ref4 has a value 0x00000592 that is not in the current compile unit in the .debug_info section. 0x000009a9: DIE attribute 0x000009ae: AT_type/FORM_ref4 has a value 0x000001c2 that is not in the current compile unit in the .debug_info section. 0x00000b85: DIE attribute 0x00000b8a: AT...

...get: > > - On OS X, with the "small" test cases I created, I get no errors at > all. > - On OS X, with my normal unit tests (with the standard library) I get > hundreds of error messages of the following form: > > 0x00000882: DIE attribute 0x00000883: AT_type/FORM_ref4 has a value > 0x00000592 that is not in the current compile unit in the .debug_info > section. > > > This indicates that while DwarfDebug.cpp was preparing dwarf info, it > created a DIE 0x00000592 that was referred by another DIE 0x00000883 but > somehow DIE 0x0000...

...ful in this case. Here's what I get: > On OS X, with the "small" test cases I created, I get no errors at all. > On OS X, with my normal unit tests (with the standard library) I get hundreds of error messages of the following form: > 0x00000882: DIE attribute 0x00000883: AT_type/FORM_ref4 has a value 0x00000592 that is not in the current compile unit in the .debug_info section. This indicates that while DwarfDebug.cpp was preparing dwarf info, it created a DIE 0x00000592 that was referred by another DIE 0x00000883 but somehow DIE 0x00000592 was not emitted. This could b...

...On OS X, with the "small" test cases I created, I get no errors at >> all. >> - On OS X, with my normal unit tests (with the standard library) I get >> hundreds of error messages of the following form: >> >> 0x00000882: DIE attribute 0x00000883: AT_type/FORM_ref4 has a value >> 0x00000592 that is not in the current compile unit in the .debug_info >> section. >> >> >> This indicates that while DwarfDebug.cpp was preparing dwarf info, it >> created a DIE 0x00000592 that was referred by another DIE 0x00000883 but...

...AT_frame_base( rbp ) > AT_MIPS_linkage_name( "_Z3bari" ) > AT_name( "bar" ) > AT_decl_file( "/llvm_cmake/test.cc <http://test.cc/>" ) > AT_decl_line( 1 ) > AT_type( {0x00000057} ( int ) ) > AT_external( true ) > > 0x00000047: TAG_formal_parameter [3] > AT_location( 0x00000000 > 0x0000000000000000 - 0x00000000000000b9: rdi+0 > 0x00000000000000b9...

Hey guys, Frederic is introducing the expression dumping support and in the interests of tersity is skipping the "DW_" in every "DW_OP" (heck, we could even skip the "OP" given the context - nothing else textual can appear there, right?) Any thoughts on skipping the "DW_" (maybe even the AT/TAG/FORM too) in the rest of dwarfdump? (skipping the AT/TAG (FORM

...e( rbp ) >> AT_MIPS_linkage_name( "_Z3bari" ) >> AT_name( "bar" ) >> AT_decl_file( "/llvm_cmake/test.cc <http://test.cc/>" ) >> AT_decl_line( 1 ) >> AT_type( {0x00000057} ( int ) ) >> AT_external( true ) >> >> 0x00000047: TAG_formal_parameter [3] >> AT_location( 0x00000000 >> 0x0000000000000000 - 0x00000000000000b9: rdi+0 >>...

...pc( 0x00000184 ) AT_frame_base( rbp ) AT_MIPS_linkage_name( "_Z3bari" ) AT_name( "bar" ) AT_decl_file( "/llvm_cmake/test.cc<http://test.cc/>" ) AT_decl_line( 1 ) AT_type( {0x00000057} ( int ) ) AT_external( true ) 0x00000047: TAG_formal_parameter [3] AT_location( 0x00000000 0x0000000000000000 - 0x00000000000000b9: rdi+0 0x00000000000000b9 - 0x0000000000000184: rsp+16, de...

...get: > > - On OS X, with the "small" test cases I created, I get no errors at > all. > - On OS X, with my normal unit tests (with the standard library) I get > hundreds of error messages of the following form: > > 0x00000882: DIE attribute 0x00000883: AT_type/FORM_ref4 has a value > 0x00000592 that is not in the current compile unit in the .debug_info > section. > > > This indicates that while DwarfDebug.cpp was preparing dwarf info, it > created a DIE 0x00000592 that was referred by another DIE 0x00000883 but > somehow DIE 0x0000...

Hi,   I want to list some additional information on this.   The variable collection I am looking at is, "variables 'declared' in scope".   1. When I traverse the MachineInstructions in the LexicalScopes ranges, and check for variables, I get variables used in this scope.      The variables listed include variables which may not have been declared in the scope. (for example

...0048: TAG_subprogram [3] AT_MIPS_linkage_name( "_main" ) AT_name( "foo" ) AT_decl_file( "/Users/joe/Documents/Code/others/clay/foo.clay" ) AT_decl_line( 1 ) AT_type( {0x0000005c} ( Int32 ) ) AT_external( 0x01 ) AT_declaration( 0x01 ) 0x0000005b: NULL 0x0000005c: TAG_base_type [4] AT_name( "Int32" ) AT_encoding( DW_ATE_signed ) AT_byte_size( 0x0...

...3] >                      AT_MIPS_linkage_name( "_main" ) >                      AT_name( "foo" ) >                      AT_decl_file( > "/Users/joe/Documents/Code/others/clay/foo.clay" ) >                      AT_decl_line( 1 ) >                      AT_type( {0x0000005c} ( Int32 ) ) >                      AT_external( 0x01 ) >                      AT_declaration( 0x01 ) > > 0x0000005b:         NULL > > 0x0000005c:     TAG_base_type [4] >                  AT_name( "Int32" ) >                  AT_encoding( DW_ATE_signe...

https://bugzilla.mindrot.org/show_bug.cgi?id=1420 Summary: BSM support on Mac OS X Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: Other OS/Version: Mac OS X Status: NEW Severity: normal Priority: P2 Component: Miscellaneous AssignedTo: bitbucket at mindrot.org

Hi, [ I think I put the most important contributors to the DebugInfo stuff in Cc:. Is there anyone else that I am missing? ] Just a short notice that I am currently working on making llvm-dwarfdump more developer friendly. There are quite a few features in Darwin’s dwarfdump that we find quite useful and that we would like to contribute to llvm-dwarfdump. I have started by augmenting the

Bunch of initially unrelated context: * type units can be referenced in a variety of ways: * DW_FORM_ref_sig8 on any attribute needing to reference the type * DW_AT_signature on a declaration of the type * extra wrinkle: the declaration can be nested into the appropriate namespace and given a name, or not * LLVM always does the "most expressive"/expensive thing: a full

Hi, Since almost all operations in the FUSE low-level API identify files by inode number, I''ve been using zfs_zget() to get the corresponding znode/vnode in order to call the corresponding VFS function in zfs_vnops.c. However, there are some cases when zfs_zget() behaves slightly different than I need: 1) If zp->z_unlinked != 0 then zfs_zget() returns ENOENT. I need it to return