search for: abbrev

...ce the problem -- I'm using clang/LLVM 3.7.1 built from source on Ubuntu 14.04. I compile the attached file with: $ clang -O1 -g test.c -lpthread If I run: $ readelf --debug-dump=info ./a.out I see the following debugging information in the binary for "main": <1><a7>: Abbrev Number: 7 (DW_TAG_subprogram) <a8> DW_AT_low_pc : 0x400880 <b0> DW_AT_high_pc : 0xc9 <b4> Unknown AT value: 3fe7: 1 <b4> DW_AT_frame_base : 1 byte block: 57 (DW_OP_reg7 (rsp)) <b6> DW_AT_name : (indirect string, of...

...================================================================= Asm -O0 ======================================================================== .file "a.c" .file 1 "/home/marco/clang_issue/a.c" .section .debug_info,"", at progbits .Lsection_info: .section .debug_abbrev,"", at progbits .Lsection_abbrev: .section .debug_aranges,"", at progbits .section .debug_macinfo,"", at progbits .section .debug_line,"", at progbits .Lsection_line: .section .debug_loc,"", at progbits .section .debug_pubnames,"", at...

Hello, I'm trying the latest rsync(3.0.0prev7) on Mac OS 10.5.1 and getting the following error: rsync: writefd_unbuffered failed to write 887 bytes [sender]: Broken pipe (32) recv_xattr_request: internal abbrev error! rsync: connection unexpectedly closed (26242 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.0pre7] Can someone explain what an internal abbrev error is? The rsync is to an attached firewire disk using: rsync --acls --xa...

...Attribute() function to CGDebugInfo, which allows other parts of clang issue auxiliary information through an enumeration type in Dwarf information. For example, by calling DI->EmitTypeAuxAttribute(type, "ID", 1234); We can get following information in dwarf: <1><3f>: Abbrev Number: 3 (DW_TAG_structure_type) <40> DW_AT_name : (indirect string, offset: 0xeb): my_str ... <2><47>: Abbrev Number: 4 (DW_TAG_member) <48> DW_AT_name : (indirect string, offset: 0xe3): x <4c> DW_AT_type : <0x6d>...

...; { > int a = 11; > int b = 22; > int c = a+b; > return c; > } > > ###################################### > # asm including dwarf debugging info > .file "test.c" > .section .debug_info,"", at progbits > Lsection_info: > .section .debug_abbrev,"", at progbits > Lsection_abbrev: > .section .debug_aranges,"", at progbits > .section .debug_macinfo,"", at progbits > .section .debug_line,"", at progbits > Lsection_line: > .section .debug_loc,"", at progbits > .section .de...

https://bugzilla.samba.org/show_bug.cgi?id=10579 Summary: --xattr internal abbrev error Product: rsync Version: 3.1.0 Platform: All OS/Version: Mac OS X Status: NEW Severity: major Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: samba at haravikk.com...

I''m looking to store the current params into a/some cookie(s). This works: @params.each_pair do |this_index, this_param| cookies[this_index] = this_param end Except, I get session-only cookies. This doesn''t work: @params.each_pair do |this_index, this_param| cookies[this_index] = { :value => this_param, :expires => 30.days.from_now } end

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

...(Backend files) will construct the dwarf data, especially debug_info. Thanks in Advance, Nagaraju > > > > Below is a sample output of the debug dump. > > > > Compilation Unit @ offset 0x0: > > Length: 0x6a (32-bit) > > Version: 4 > > Abbrev Offset: 0x0 > > Pointer Size: 4 > > <0><b>: Abbrev Number: 1 (DW_TAG_compile_unit) > > <c> DW_AT_producer : (indirect string, offset: 0x0): clang > > version 8.0.1 > > <10> DW_AT_language : 12 (ANSI C99) > >...

...iscriminant object, and then wish to use 'plot.lda' to do the plot on this object like below. drug.lda <- lda(Inhibition ~ NET_CHARGE + PKA_1 + MW + MLOGP, data = drug.class, method = "moment") plot.lda(drug.lda, panel = panel.lda, cex = 0.7, dimen = 1, abbrev = FALSE, type ="density") but I got an error message: Error: couldn't find function "plot.lda" and then I tried plot(drug.lda, panel = panel.lda, cex = 0.7, dimen = 1, abbrev = FALSE, type ="density") still an error message was returne...

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

...C++03 say the same. > Seems to be problem with qualifier type but was wondering how is this > target dependent? I think it's the gdb programs that are printing different things for the same DWARF debug information. Dumping the information from the x86 binary gives: <1><6b>: Abbrev Number: 6 (DW_TAG_class_type) <6c> DW_AT_name : (indirect string, offset: 0x3e): Simple <70> DW_AT_byte_size : 1 <71> DW_AT_decl_file : 1 <72> DW_AT_decl_line : 1 [...] <3><7f>: Abbrev Number: 8 (DW_TAG_formal_parameter) &...

...in to the generated debug dump from the object file I found that DW_AT_name is always (indirect string, offset: 0x0): clang version 8.0.1, instead of variable names. Below is a sample output of the debug dump. Compilation Unit @ offset 0x0: Length: 0x6a (32-bit) Version: 4 Abbrev Offset: 0x0 Pointer Size: 4 <0><b>: Abbrev Number: 1 (DW_TAG_compile_unit) <c> DW_AT_producer : (indirect string, offset: 0x0): clang version 8.0.1 <10> DW_AT_language : 12 (ANSI C99) <12> DW_AT_name : (indirect string, offset:...

Hi All, Was looking into a simple program - class Simple { public: void fun() {} }; int main() { Simple s; s.fun(); return 0; } When compiled using clang++ for ARM- Expected result when we run - print Simple::fun in GDB is void fun(Simple* const this) as this should be a const pointer but in case of arm compiled binary we get void fun(Simple* this). Works fine when compiled using

Features: * Management WEBrick - start, stop * Viewing log files * Abbrev from TextMate * Switching between View/Action http://www.emacswiki.org/cgi-bin/emacs/rails.el

Hi, > Suppose I have the following source: > > file1: > #include "file2" > #include "file3" > int fn1(void) ... > > file2: > int a; > > file3: > int fn2(void) ... > > then fn1, along with all the base types etc appear to be in compile unit > "file1", the variable a appears to be in compile unit

...hanks in Advance, >> Nagaraju >> > > >> > > Below is a sample output of the debug dump. >> > > >> > > Compilation Unit @ offset 0x0: >> > > Length: 0x6a (32-bit) >> > > Version: 4 >> > > Abbrev Offset: 0x0 >> > > Pointer Size: 4 >> > > <0><b>: Abbrev Number: 1 (DW_TAG_compile_unit) >> > > <c> DW_AT_producer : (indirect string, offset: 0x0): clang >> > > version 8.0.1 >> > > <10> DW_AT_l...

...itstreamReader.h b/include/llvm/Bitcode/BitstreamReader.h > index 3daef78..840f57e 100644 > --- a/include/llvm/Bitcode/BitstreamReader.h > +++ b/include/llvm/Bitcode/BitstreamReader.h > @@ -409,7 +409,7 @@ public: > } > > /// EnterSubBlock - Having read the ENTER_SUBBLOCK abbrevid, enter > - /// the block, and return true if the block is valid. > + /// the block, and return true if the block has an error. > bool EnterSubBlock(unsigned BlockID, unsigned *NumWordsP = 0) { > // Save the current block's state on BlockScope. > BlockScope.push_b...

...attribute of DW_TAG_compile_unit? This prevents using language codes in the DW_LANG_lo_user=0x8000 to DW_LANG_hi_user=0xffff range. I think the obvious change to use DW_FORM_data2 in line 1897 of lib/CodeGen/AsmPrinter/DwarfDebug.cpp should fix it. Or, if there are binary compatibility issues, the abbrev form could be chosen conditionally. Are there? Thanks -Peter S. Housel- housel at acm.org

I have a question about the llvm debugging records, especially wrt compile units. In the non-LLVM sense, a compile unit is essentially everything contained within a single .o file, and it is derived from one or more source and header files. Included in a compile unit are functions and global data. Dwarf records refer to compile units in the same way: a compile unit record has children which