similar to: xfer_sum_len type bug

Displaying 10 results from an estimated 10 matches similar to: "xfer_sum_len type bug"

2012 Jun 15
1
Problem with active resource(500 internal server error)
Hi, I have a rails server running. I wanted to connect to this using activeresource. Executing this code Class Buildclient < ActiveResource::Base self.site = "http://localhost:3000/builds" end builds = Buildclient.find(:all) puts builds (## printed nil) On the rails server terminal i see Started GET "/builds/buildclients.json" for 127.0.0.1 at Fri Jun 15 10:34:05
2020 Sep 27
1
strange crash with md5p8.diff + xxhash
With rsync-patches/md5p8.diff and --enable-xxhash % gdb --args ./rsync --version Using host libthread_db library "/lib64/libthread_db.so.1". rsync version v3.2.3-29-ge55788bd protocol version 31 Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others. Web site: https://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints,
2019 Dec 03
5
clang and -D_FORTIFY_SOURCE=1
Hi folks (CCing llvm-dev, but that's probably more of a cfe-dev topic), As a follow-up to that old thread about -D_FORTIFY_SOURCE=n http://lists.llvm.org/pipermail/cfe-dev/2015-November/045845.html And, more recently, to this fedora thread where clang/llvm -D_FORTIFY_SOURCE support is claimed to be only partial: https://pagure.io/fesco/issue/2020 I dig into the glibc headers in
2019 Dec 04
2
[cfe-dev] clang and -D_FORTIFY_SOURCE=1
> Are you sure you've diagnosed the issue correctly? __builtin___memcpy_chk works correctly, as far as I know. 100% sure. Let's have a look at the output of #include <string.h> static char dest[10]; char* square(int n) { memcpy(dest, "hello", n); return dest; } compiled with -D_FORTIFY_SOURCE=1 -O1 : https://godbolt.org/z/UvABWp Clang issues a call to
2009 Feb 25
3
regexp capturing group in R
Hello, Newbie question: how do you capture groups in a regexp in R? Let's say I have txt="blah blah start=20080101 end=20090224". I'd like to get the two dates start and end. In Perl, one would say: my ($start,$end) = ($txt =~ /start=(\d{8}).*end=(\d{8})/); I've tried: txt <- "blah blah start=20080101 end=20090224" m <-
2023 Jun 06
1
Possible overflow bug?
While doing some related work I built openssh 9.3p1 with -fsanitize=address and this came up during compilation. In file included from /usr/include/string.h:535, from kex.c:34: In function 'explicit_bzero', inlined from 'kex_free_newkeys' at kex.c:743:2: /usr/include/bits/string_fortified.h:72:3: warning: '__explicit_bzero_chk' writing 48 bytes
2012 Oct 10
4
[Bug 55832] New: xf86-video-nouveau-1.0.2 - Xorg crashes once a week : segmentation fault in NVRefreshArea
https://bugs.freedesktop.org/show_bug.cgi?id=55832 Priority: medium Bug ID: 55832 Assignee: nouveau at lists.freedesktop.org Summary: xf86-video-nouveau-1.0.2 - Xorg crashes once a week : segmentation fault in NVRefreshArea QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified
2018 Mar 07
3
[Bug 105382] New: segfault in nouveau_scratch_data when using 2 nouveau cards
https://bugs.freedesktop.org/show_bug.cgi?id=105382 Bug ID: 105382 Summary: segfault in nouveau_scratch_data when using 2 nouveau cards Product: Mesa Version: 17.0 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau
2016 Dec 20
1
Latest Dovecot v2.2.devel (9bc8d9b) crashes on login and lmtp
I was unable to produce an IMAP core but have been successful with LMTP. Basically it crashes right upon login or delivery: Dec 20 08:55:23 nihlus dovecot: master: Dovecot v2.2.devel (9bc8d9b) starting up for imap, lmtp Dec 20 08:56:15 nihlus dovecot: imap(tlx at leuxner.net): Fatal: master: service(imap): child 5710 killed with signal 11 (core not dumped) Dec 20 08:57:23 nihlus dovecot:
2012 Dec 01
0
[LLVMdev] problem trying to write an LLVM register-allocation pass
On 11/30/2012 6:36 PM, Lang Hames wrote: > > > RBP is used as the frame pointer on x86 (hence its automatic > appearance in your code), and shouldn't be allocated to any vreg in > function bar. Loading/saving RBP should be managed by the stack frame > setup/teardown code. > If it doesn't already, your allocator should filter out reserved > registers (See