search for: fragilities

I'd like to be able to have "weak" references to global variables. Now, currently LLVM allows global values to have "weak" linkage type (and variants thereof), but this is a different meaning of the word "weak" - what I'm thinking of is similar to the concept of weak references in Java and other languages that support garbage collection, except that the

Hi all, quite a few tests use the pattern "2>&1 | FileCheck %s". AFAIK how stdout and stderr are merged into a single character stream is undefined and depends e.g. on whether stdout is buffered. I think we are often saved by the fact that standard output is written only at the end of the program and stderr is unbuffered, i.e. always written before stdout. A lot of tests disable

Philip Reames via cfe-dev <cfe-dev at lists.llvm.org> writes: > A challenge we already have - as in, I've broken these tests and had to > fix them - is that an end to end test which checks either IR or assembly > ends up being extraordinarily fragile.  Completely unrelated profitable > transforms create small differences which cause spurious test failures.  > This is

Park, I was just playing around with the Process.fork/wait that you committed. I discovered that it''s rather easy to break with this: require "win32/process" include Win32 Dir.chdir ".." # This causes the problem pid = Win32::Process.fork if pid == 0 puts "In the child" exit else puts "In the parent" end Win32::Process.wait(pid) I think

__set_tss_desc has a complex calculation of the TSS segment limit, duplicating the quirky details of the I/O bitmap array length, and requiring a complex comment to explain. Replace that calculation with a simpler one based on the offsetof the "stack" field that follows the array. That then removes the last use of IO_BITMAP_OFFSET, so delete it. Signed-off-by: Josh Triplett <josh

On 10/30/2013 03:22 PM, Kees Cook wrote: >> >> - /* >> - * sizeof(unsigned long) coming from an extra "long" at the end >> - * of the iobitmap. See tss_struct definition in processor.h >> - * >> - * -1? seg base+limit should be pointing to the address of the >> - * last valid byte > > I think it

__set_tss_desc has a complex calculation of the TSS segment limit, duplicating the quirky details of the I/O bitmap array length, and requiring a complex comment to explain. Replace that calculation with a simpler one based on the offsetof the "stack" field that follows the array. That then removes the last use of IO_BITMAP_OFFSET, so delete it. Signed-off-by: Josh Triplett <josh

On Thu, 27 Aug 2015, Bostjan Skufca wrote: > Are you connecting by specifying "ssh HOSTNAME" instead of "ssh IP.IP.IP.IP"? > > If this is the case, then "Host 192.168.*.*" line never matches when > you think it should. > > From ssh_config manpage: > "The host is the hostname argument given on the command line (i.e. the > name is not

On Fri, Sep 20, 2019 at 09:33:06AM -0500, Eric Blake wrote: > Checking for file existence for filters is somewhat less fragile than > for plugins, because all filters are built in-tree (we've specifically > documented that we don't provide ABI guarantees for filters, so the only > sane way to use a filter is to compile it at the same time/version as > the nbdkit binary that

>> 1. Guest allocates a page and sends it to the host. >> 2. Shrinker gets active and releases that page again. >> 3. Some user in the guest allocates and modifies that page. The dirty bit is >> set in the hypervisor. > > The bit will be set in KVM's bitmap, and will be synced to QEMU's bitmap when the next round starts. > >> 4. The host processes

I''m trying to work out the most reasonable way to keep track of users "voting" for or against a particular bit of data. Obviously, I don''t want them to be able to just bang on the link -- I''d prefer to limit it to one vote per day, for example. I could record the fact that they''ve voted in the session, but I''d really rather not have

>> 1. Guest allocates a page and sends it to the host. >> 2. Shrinker gets active and releases that page again. >> 3. Some user in the guest allocates and modifies that page. The dirty bit is >> set in the hypervisor. > > The bit will be set in KVM's bitmap, and will be synced to QEMU's bitmap when the next round starts. > >> 4. The host processes

I would like to set the 'xlab' on the 'upper' x axis. The following code shows roughly what I want by way of (one possible) expected behaviour. par(mar=c(5.1, 4.1, 5.1, 2.1)) plot(rnorm(10), rnorm(10), xlab="the lower one") axis(3, xlab="the upper one????") There are various other ways that could be expected to work, but hopefully the above is clear enough to

Dear [R] and beamer community, I am trying to build a presentation using beamer and [R]. I can Sweave the file; however, when I run pdflatex on the file i get the following error: ! FancyVerb Error: Extraneous input `> a = 123450 > b = -0.69 \end {Sinput} \end {Schunk} \end { beamer at frameslide}\ifbeamer at twoscreenstext \beamer at dosecondscreennow {{fragile} \frametitle

Hi, I am having trouble getting \alt (or \altenv) to work with Schunk/Sinput and was wondering if anybody had had success? With the slide \begin{frame}[fragile]\frametitle{Basic R} \alt<2>{ <<echo=TRUE>>= 2+2 @ }{ <<echo=TRUE, eval=FALSE>>= 2+2 @ } \end{frame} I get the error message: ! FancyVerb Error: Extraneous input `> 2+2 \end {Sinput} \end

> That makes it fragile, and that’s why I disagree with your “90% done” assessment. > What if the service behing the hook is down for a few days? In the long-term view, a pretty trivial catch-up script ought to be able to synthesize a sane history after any amount of down-time. People could even run it locally for their bisecting needs if it was that important to them. In the short term, I

On Tue, 8 Mar 2016, Pete Batard via Syslinux wrote: > would. As I mentioned, I've seen reports of ISOHybrids that didn't boot in DD > mode, but that seemed to work using the Rufus process. And you will always be > limited by what the "automated process" that is the ISOHybrid algorithm can > do (which can of course be modified by a developer, but so can Rufus'

Hi Josh, On Tue, Oct 22, 2013, at 3:34, Josh Triplett wrote: > __set_tss_desc has a complex calculation of the TSS segment limit, > duplicating the quirky details of the I/O bitmap array length, and > requiring a complex comment to explain. Replace that calculation with a > simpler one based on the offsetof the "stack" field that follows the > array. > > That then

Hi Josh, On Tue, Oct 22, 2013, at 3:34, Josh Triplett wrote: > __set_tss_desc has a complex calculation of the TSS segment limit, > duplicating the quirky details of the I/O bitmap array length, and > requiring a complex comment to explain. Replace that calculation with a > simpler one based on the offsetof the "stack" field that follows the > array. > > That then

Hi Using this line in dovecot.conf (ignore linewrap) default_mail_env = mbox:%h/IMAP/:INBOX=%h/.email:INDEX=/var/cache/dovecot/%n The INBOX indexes are being built correctly in /var/cache/dovecot, but all other indexes for folders are still being built in the user's home directory. I had it working once - but it seems fragile - almost as if the config parser is sensitive to context???