search for: repro

...on User yubacity Group yubacity #DefaultChdir /var/ftp/pub/ RequireValidShell off <Limit STOR> AllowAll </Limit> <Limit WRITE> AllowAll </Limit> </Anonymous> # ## ### #### RePro Accounts ##### ### ## # <Anonymous /var/ftp/repro/teichert> AnonRequirePassword on User teichert Group teichert #DefaultChdir /var/ftp/pub/ RequireValidShell off <Limit STOR> AllowAll &...

All, Recently I ran across a URL documenting published research using R: http://www.cgd.ucar.edu/ccr/ammann/millennium/CODES_MBH.html A note on the site indicates that the code is being revised. The code and data are provided, so that one could reproduce the results without having to buy a proprietary software program. In poking around the R website it is clear that a lot of thought has gone into documenting reproducible research, notably by Harrell, Gentleman, and the Sweave effort, among others. http://biostat.mc.vanderbilt.edu/twiki/bin/vie...

...g.declare to llvm.dbg.value at all, no other > changes -- doesn't work, in the way I expected it to not work > > I tried removing the call to llvm::LowerDbgDeclare that's being made > by the coroutine passes. The IR and DWARF dump after having done so > are in the files 'repro.declare.ll' and 'repro.declare.dwarf.txt'. > > Using an executable built from this IR, I can use lldb to break at the > line where the declare exists, > https://gist.github.com/modocache/8a7b12eb42012990ba534787c4a47275#file-repro-declare-ll-L167 <https://gist.github.com...

Hi folks, I'm hitting the below assertion failure when compiling this small piece of C code (repro.c, attached). My command line is: bin/clang --target=aarch64-linux-gnu -c -O2 repro.c clang is built from top of trunk as of this morning. It only happens at -O2, and it doesn't happen with the default target (x86_64). I tried to reproduce using just 'llc -O2' but didn't manage -...

Hi Brian, On Tue, Feb 25, 2020 at 7:43 PM Brian Gesiak <modocache at gmail.com> wrote: > In other words, the value of %i is stored on the frame object, on the > heap, at an offset of 7 into the frame. I'm beginning to think a > fundamental fix for this issue would be to stop replacing > llvm.dbg.declare with llvm.dbg.value, and instead replace the > llvm.dbg.declare with

...39;replaceDbgDeclare' called multiple times, and it reuses the result of a single getelementptr instruction. Because of this, only the last invocation results in correct debug info being produced. Put another way: when I place a breakpoint in my example on the last instance that %i is reloaded, repro.cpp:45 at https://gist.github.com/modocache/6f29093ba2827946011b422ed3bd2903#file-repro-cpp-L45, I get the correct debug info: i = 3, j = 2. In every other spot, I get 'error: Couldn't materialize: couldn't get the value of variable i: variable not available'. Still, is great progre...

I need perl-Gtk2 for TinyCA2. I find it on centos.karan.org After many misteps, I add bout kbsingh-Centos-Extras.repro and kbsingh-Centos-Misc.repro to /etc/yum.repro.d I do a yum install perl-Glib and it finally goes, adding perl-ExtUtils and warning me about user mockbuild does not exist. Then I try install perl-Gtk2 and it fails: yum install perl-Gtk2 Setting up Install Process Setting up repositories Read...

...because ObjectFile::createObjectFile() does not support creating objects of bitcode type and thus llvm-ar cannot read them to retrieve the symbol information. Is there a plan to add support back to llvm-ar to generate symbol table information when archiving bitcode files? Thanks, Jason Steps to reproduce: Create repro.c with the following contents: const char* symbol = "Hello, World!"; Create archive containing llvm bitcode files (no symbol table created): clang -emit-llvm -c -o repro.bc repro.c llvm-ar rs repro.a repro.bc Create archive containing object files (symbol table is crea...

Helo, I'm trying to update a centos server with a kernel form the centos.plus repro because it contain Firewire/IEEE1394 support. But when y do a : # yum update The kernel from the base is more recent thant the centos plus repro I have tried with the http://wiki.centos.org/PackageManagement/Yum/Priorities plug-in and it didn't take the right kernel : ftp://ftp.free.fr/mirror...

I've just done a test with a WebRTC client connecting to the repro proxy with the SIP messages relayed over TCP to Asterisk Asterisk successfully answers the call using SAVPF, SRTP and ICE. The client is greeted by the demo This was tested in the Asterisk 11 environment described in my earlier email about SRTP build issues on the asterisk-users list. This is q...

...yzkaller.appspot.com/x/report.txt?x=1686ad27200000 > console output: https://syzkaller.appspot.com/x/log.txt?x=1286ad27200000 > kernel config: https://syzkaller.appspot.com/x/.config?x=c94f9f0c0363db4b > dashboard link: https://syzkaller.appspot.com/bug?extid=d21e6e297322a900c128 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=141db34d400000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=108ef293400000 > > Reported-by: syzbot+d21e6e297322a900c128 at syzkaller.appspotmail.com > Fixes: 6b1e6cc7 ("vhost: new device IOTLB API")

...yzkaller.appspot.com/x/report.txt?x=1686ad27200000 > console output: https://syzkaller.appspot.com/x/log.txt?x=1286ad27200000 > kernel config: https://syzkaller.appspot.com/x/.config?x=c94f9f0c0363db4b > dashboard link: https://syzkaller.appspot.com/bug?extid=d21e6e297322a900c128 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=141db34d400000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=108ef293400000 > > Reported-by: syzbot+d21e6e297322a900c128 at syzkaller.appspotmail.com > Fixes: 6b1e6cc7 ("vhost: new device IOTLB API")

...njay, who touched this last. :-) > > On Wed, Jul 20, 2016 at 12:44 PM, Ismail Badawi (ibadawi) via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi folks, >> >> I'm hitting the below assertion failure when compiling this small piece >> of C code (repro.c, attached). >> >> My command line is: >> >> bin/clang --target=aarch64-linux-gnu -c -O2 repro.c >> >> clang is built from top of trunk as of this morning. It only happens at >> -O2, and it doesn't happen with the default target (x86_64). I tried to &g...

...hase in https://llvm.org/PR43035 still persists: CMake Error at /usr/lib/llvm-9/lib/cmake/llvm/LLVMExports.cmake:1323 (message):   The imported target "yaml-bench" references the file      "/usr/lib/llvm-9/bin/yaml-bench"   but this file does not exist. Here's a minimal repro: https://travis-ci.org/weliveindetail/apt-llvm-9-dev-repro/builds/619590445#L204 Is anyone else seeing this too? Is there an obvious fix that I don't see? What's your workarounds? My current workaround is ridiculous, but works for me: https://github.com/weliveindetail/apt-llvm-9-dev-repro...

...nst int k; }; > template<typename T> const int U<T>::k = T::x; > > #ifdef TU1 > extern int f(); > const int S::x = 42; > int main() { return f() + U<S>::k; } > #endif > > #ifdef TU2 > int f() { return U<S>::k; } > #endif > > /* Steps to repro: > > clang repro.cpp -DTU1 -c -o tu1.o > clang repro.cpp -DTU2 -c -o tu2.o > clang tu1.o tu2.o > ./a.out > > */ > > This segfaults, because... in TU1, we get: > > @_ZN1UI1SE1kE = weak_odr constant i32 42, align 4 > > and in TU2, we get: > > @_ZN1UI1SE1kE...

...int x; }; template<typename T> struct U { static const int k; }; template<typename T> const int U<T>::k = T::x; #ifdef TU1 extern int f(); const int S::x = 42; int main() { return f() + U<S>::k; } #endif #ifdef TU2 int f() { return U<S>::k; } #endif /* Steps to repro: clang repro.cpp -DTU1 -c -o tu1.o clang repro.cpp -DTU2 -c -o tu2.o clang tu1.o tu2.o ./a.out */ This segfaults, because... in TU1, we get: @_ZN1UI1SE1kE = weak_odr constant i32 42, align 4 and in TU2, we get: @_ZN1UI1SE1kE = weak_odr global i32 0, align 4 plus a global constructor whic...

...een fixed. I > further reduced it. Seems to be related to symbol versioning. We don't > recognize that `.symver bar, foo@@VERS` is a definition of `foo`. > ) > > > If you are building your own LLD, can you see if the attached patch fixes > it for you? If not, can you add `--reproduce /tmp/repro.tar` to your link > command line and upload repro.tar somewhere for us? > Thanks! I applied that patch and it links with -flto now, but it looks like there are now some other problems. First, it seems to be dropping things that I try to KEEP in the linker script, even when I d...

...Jul 20, 2016 at 12:44 PM, Ismail Badawi (ibadawi) via llvm-dev >>> <llvm-dev at lists.llvm.org> wrote: >>>> >>>> Hi folks, >>>> >>>> I'm hitting the below assertion failure when compiling this small piece >>>> of C code (repro.c, attached). >>>> >>>> My command line is: >>>> >>>> bin/clang --target=aarch64-linux-gnu -c -O2 repro.c >>>> >>>> clang is built from top of trunk as of this morning. It only happens at >>>> -O2, and it doesn'...

...Assignee: wayned at samba.org Reporter: andras at nagya.net QA Contact: rsync-qa at samba.org This bug was previously reported on the rsync mailing list, https://lists.samba.org/archive/rsync/2018-April/031626.html . This version of the report has a slightly more detailed repro, and was produced on Linux. The bug manifests if an xattr filter rule is being used; however the repro does not require actual xattrs to be present, so the bug can be reproduced even if the file system being used does not support xattrs. Prerequisites for the repros: - ssh service running on loca...

...ct.txt?x=118810bfa00000 > start commit: 13bf6d6a Add linux-next specific files for 20190725 > git tree: linux-next > kernel config: https://syzkaller.appspot.com/x/.config?x=8ae987d803395886 > dashboard link: https://syzkaller.appspot.com/bug?extid=36e93b425cd6eb54fcc1 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15112f3fa00000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=131ab578600000 > > Reported-by: syzbot+36e93b425cd6eb54fcc1 at syzkaller.appspotmail.com > Fixes: 0ecfebd2b524 ("Linux 5.2") > > For information...