similar to: internal abbrev error! ?

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

Hi everyone, I'm trying to get debug information for a C/pthreads application, but it seems like clang/LLVM are producing limited & erroneous debugging information. I've attached a simple test example to reproduce 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

Sorry, this is the attachment. 2014-02-19 15:08 GMT+08:00 杨勇勇 <triple.yang at gmail.com>: > Thank you. > > Here is an example and the attchment contains extra files including object > file and executable file. > I want to print for example the value of "a", but lldb command "frame > variable a" displays "0" and so does "b", and

This patch adds EmitTypeAuxAttribute() 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

Hi Karthik, > 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). I believe the actual type is coming from CXXMethodDecl::getThisType, which quotes the standard as saying: // C++ 9.3.2p1: The type of this in a member function

https://bugzilla.samba.org/show_bug.cgi?id=5365 Summary: --backup and --xattrs are not compatible Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Other Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: fauthier@free.fr

On Tue, Apr 21, 2020 at 6:16 PM Robinson, Paul <paul.robinson at sony.com> wrote: > > > > > -----Original Message----- > > From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of Nagaraju > > Mekala via llvm-dev > > Sent: Tuesday, April 21, 2020 6:04 AM > > To: jh7370.2008 at my.bristol.ac.uk > > Cc: LLVM Developers Mailing List

Hi there, I am a master student in Denmark, and apply R to analyze the drug data. I use the function 'lda' to obtain a linear discriminant 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,

Hi James, Thanks for reply. When I looked 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

On Wed, Apr 22, 2020 at 10:34 PM David Blaikie <dblaikie at gmail.com> wrote: > > > > On Wed, Apr 22, 2020 at 9:28 AM Nagaraju Mekala via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> On Tue, Apr 21, 2020 at 6:16 PM Robinson, Paul <paul.robinson at sony.com> wrote: >> > >> > >> > >> > > -----Original Message-----

Hi Jan, > I've been looking into how to make llvm bitcode files smaller. There is one > simple change that appears to shrink linked bitcode files by about 15%. See > this spreadsheet for some rough data: > > https://docs.google.com/spreadsheet/ccc?key=0AjRrJHQc4_bddEtJdjdIek5fMDdIdFFIZldZXzdWa0E the improvement is wonderful! ... > In any case, the patch is attached if

I'm using rsync 3.0.7 on Mac OS X 10.6, compiled according to Mike Bombich's instructions at http://www.bombich.com/rsync.html. Rsync repeatedly exits with a protocol data stream error when trying to copy some com.apple.FinderInfo extended attributes. While testing this issue, I found that rsync is not actually copying all extended attributes even when there is no error message. I'm

Dear list, Working the example in Stats complements to V&R 3rd ed., I found this : > library(MASS) > library(mva) > data(farms) > plot(mca(farms,abbrev=TRUE),cex=rep(0.7,2)) # ... Works OK # Sheer curiosity ... > plot(mca(farms,abbrev=TRUE,nf=4),cex=rep(0.7,2)) Error in rep(p * X.svd$d[sec], c(n, n)) : invalid number of copies in "rep" A bit of exploration in the

Is there any good reason for using DW_FORM_data1 for the DW_AT_language 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

On Aug 10, 2018, at 1:28 PM, Marshall Clow via cfe-dev <cfe-dev at lists.llvm.org> wrote: > > * The clock stuff being added in C++20 has already been discussed here. I’ve missed the discussions on file_time_type, however I thought I should throw in my opinion here before it is too late to do anything about it. I believe it is a mistake to model file_time_type with 128 bits. It

rsync 3.0.0. MacOSX 10.5.1 Server/Intel. Trying to detect files with funny chars in their name, as I cannot find them with "find", I use the error (Illegal byte sequence) given by rsync when the target charset cannot reproduce them. While doing this I have met this error: /usr/local/bin/rsync -an --rsync-path=/usr/local/bin/rsync -- iconv=UTF8-MAC,437 /db /tmp/ rsync:

Ok, I'll submit a patch to turn that into a report_fatal_error saying you can't start an abbrev with an array or blob. Thanks, Filipe F On Fri, Jan 23, 2015 at 2:12 PM, Rafael Espíndola < rafael.espindola at gmail.com> wrote: > The restriction looks reasonable: A record starts with a code. The code > can be encoded as a literal or be part of the abbreviation. > >

Dear list, I've tried several times to wrap my head around the Design library, without much success. It does some really nice things, but I'm often uncomfortable because I don't understand exactly what it's doing. Anyway, one thing I really like is the latex.ols() function, which converts an R linear model formula to a LaTeX equation. So, I started writing a latex.lm() function

Hi During using the R(vision 2.0.1), I meet a problem. I would like to do the Multiple Correspondence Analysis, but when I use the "< mca(lf, nf = 2, abbrev = FALSE)", the sentence "Error: couldn't find function 'mca'" will appear. So, please tell me how can I use the "mca()", thanks! Any help appreciated....

Hello, Disclaimer: I have no plan to break 3.x bitcode compatibility in any way. I’m experimenting with ideas to improve the current bitcode serialization and deserialization in general. I’m interested in improving the speed and the flexibility of the reader/writer, as well as making the code easier to deal with. My current griefs against our bitcode format are mainly the lack of built-in