search for: l429

In data giovedì 25 giugno 2015 14:50:03, Richard W.M. Jones ha scritto: > We had a chat about this on IRC, and I'm not very happy about any > patch that requires a special ./configure flag. I'm not sure where you see any special ./configure flag, other than what is already there (and not used much because makes things cumbersome). > We should find a way > to enable this

...been using from time to time, even if not often. > > Can you expand a bit more on the parts you consider racy? There are two objections: (1) That we currently have separate shutdown paths in the valgrind/non-valgrind case: https://github.com/libguestfs/libguestfs/blob/master/src/handle.c#L429-L443 https://github.com/libguestfs/libguestfs/blob/master/src/conn-socket.c#L346-L364 We shouldn't have two different paths that developers and non- developers use. (2) This actually causes bugs. The second one is the race. https://bugzilla.redhat.com/show_bug.cgi?id=1023630 https://bugzill...

Hi, I've tracked down what I believe is a bug in lld's relocation processing for R_X86_64_PC32 REL relocations. I'm producing the object file in a slightly unusual way: I'm using objcopy on a relocatable i386 ELF object file to convert it to x86_64 which transforms a R_386_PC32 into a R_X86_64_PC32. Steps to reproduce: 1. Assemble the attached bug.asm using nasm and note the

I have febootstrap ported to and working on Arch, but there are a few packages missing from the main Arch repos, and the packages need to be in the main repos for the febootstrap sequence to work. So I have a few quick questions, first, how well does the supermin app work, without augeas, are zfs, gfs and hfs used only for mounting those filesystems inside the vm image, and I noticed that there is