search for: perniciously

I've come across a curious and pernicious problem in llvm-rc. absolute.test checks that llvm-rc can accept a filename that is an absolute path. And it works just fine. Until you run it with a file that starts with "/c." These will fail: llvm-rc /crawl/through/some/path/to/my.rc llvm-rc /c/some/path/to/my.rc The option parser ends up interpreting "/" as an option prefix

Hi folks I noticed something interesting when debugging a program that uses llvm for JIT compilation. Running `ltrace` surfaced a number of `getenv("bar")` calls coming from llvm. It turns out these are not "real" `getenv` calls, but are an optimization "do nothing" escape hatch which have been in `llvm/include/llvm/LinkAllPasses.h` [for over 15years](1) -

...org <samba at lists.samba.org> Subject: Re: [Samba] Rocky linux 9 - Samba AD Morning, Metin: If you need current releases of Samba for RHEL 8 or RHEL 9 equivalent systems, I publish RPM building toolkits at: https://github.com/nkadel/samba4repo/ For a while, it got weird. Red Hat was perniciously refusing to publish the "devel" parts of certain RPMs, even though used in house to build Samba RPMs. Someone changed policy, and now they're in the "Code Ready Builder" channel or even in EPEL. It also has gotten weird for Samba 4.18, which has dependencies on updated libl...

nbd_connect_unix|tcp had a tricky failure case. This is a consequence of allowing callers to mix synchronous and asynchronous calls, with multi-conn thrown into the mix. I think the new behaviour proposed here is better. We could do with a better way of classifying the state of connections, such as are they connectING. Rich.

On 5/21/19 3:44 PM, Richard W.M. Jones wrote: > If not using multi-conn then obviously the synchronous connection > calls ‘nbd_connect_unix’, ‘nbd_connect_tcp’ and ‘nbd_connect_command’ > should only return when the (one) connection object is connected. > > In the multi-conn case it's not very clear what these synchronous > calls should do. Previously I had it so that they

Not sure if this is the right place to ask. Please let me know if there's a better place. I ran the clang static analyzer via Xcode 4.6.3 on our project that uses a lot of third-party libraries. One of them is Google protobufs, and it has a set of non-exiting assertion macros that the analyzer (rightly) ignores when flagging some NULL dereferences. The macros look like this: #define

My customer has dropdowns like this: Year Month Day If you submit with month selected and year blank, it subs in a year arbitrarily. Worse still, it subs in the year 5. I have no idea why. It seems a pernicious default. Anyway, they''re developing an app, they''re a designer turned coder, turning to a real programmer (me, allegedly) to make sense of the madness they''ve

I'm not sure exactly where to point my finger with this one, but there is a nasty surprise to the unsuspecting user. There is no check on the length of the vector passed in the pch= argument to plot, it is just recycled as necessary: plot(1:10,1:10,pch=1:2) gives alternating circles and triangles. The nasty bits come up especially with plot.formula: x<-1:10;y<-1:10

On 5/22/19 4:50 AM, Richard W.M. Jones wrote: > If not using multi-conn then obviously the synchronous connection > calls ‘nbd_connect_unix’, ‘nbd_connect_tcp’ and ‘nbd_connect_command’ > should only return when the (one) connection object is connected. > > In the multi-conn case it's not very clear what these synchronous > calls should do. Previously I had it so that they

On Tue, May 21, 2019 at 05:08:05PM -0500, Eric Blake wrote: > On 5/21/19 3:44 PM, Richard W.M. Jones wrote: > > If not using multi-conn then obviously the synchronous connection > > calls ‘nbd_connect_unix’, ‘nbd_connect_tcp’ and ‘nbd_connect_command’ > > should only return when the (one) connection object is connected. > > > > In the multi-conn case it's not

On 08/12/2013 11:22, Chandler Carruth wrote: > On Sun, Dec 8, 2013 at 2:11 AM, Alp Toker <alp at nuanti.com > <mailto:alp at nuanti.com>> wrote: > > I'd like to propose deprecating and shortly thereafter removing > the lit test runner feature that concatenates RUN lines ending in > a trailing \ > > > I'm really opposed to this. Especially

Oh, right, this stuff. I guess the non-windows solution might've been a volatile read, for instance? So maybe not so much that the general machinery isn't needed, but that perhaps MSVC does something interesting with a volatile read or whatever other solution might've been used. Hmm, not sure why the whole file was added only when MSVC support was added - if it is a "static

If not using multi-conn then obviously the synchronous connection calls ‘nbd_connect_unix’, ‘nbd_connect_tcp’ and ‘nbd_connect_command’ should only return when the (one) connection object is connected. In the multi-conn case it's not very clear what these synchronous calls should do. Previously I had it so that they would return as soon as at least one connection was connected. However this

If not using multi-conn then obviously the synchronous connection calls ‘nbd_connect_unix’, ‘nbd_connect_tcp’ and ‘nbd_connect_command’ should only return when the (one) connection object is connected. In the multi-conn case it's not very clear what these synchronous calls should do. Previously I had it so that they would return as soon as at least one connection was connected. However this

Hello R friends, I'm wondering why I get funny qqnorm() results. It seems that they should all be reflected in the normal qqline(). For instance: if I qqnorm() bimodal or uniform data I get a sigmoidal in which the qqnorm() points lie above the qqline() at -ve theoretical quantiles, and the qqnorm() points lie below the qqline() at +ve theoretical quantiles. Yet I expect such platykurtic

On Sun, Dec 8, 2013 at 4:24 AM, Alp Toker <alp at nuanti.com> wrote: > > On 08/12/2013 11:22, Chandler Carruth wrote: > > On Sun, Dec 8, 2013 at 2:11 AM, Alp Toker <alp at nuanti.com> wrote: > >> I'd like to propose deprecating and shortly thereafter removing the lit >> test runner feature that concatenates RUN lines ending in a trailing \ >>

Patch 1/6 was posted before and I didn't change it: https://www.redhat.com/archives/libguestfs/2019-May/thread.html#00134 That doesn't necessarily mean I shouldn't change it, I'm posting it again because the other patches depend on it. The main change in this series is we add three new API functions: nbd_aio_is_created - connection has just been created

On Dec 8, 2013, at 4:24 AM, Alp Toker <alp at nuanti.com> wrote: > > On 08/12/2013 11:22, Chandler Carruth wrote: >> On Sun, Dec 8, 2013 at 2:11 AM, Alp Toker <alp at nuanti.com> wrote: >> I'd like to propose deprecating and shortly thereafter removing the lit test runner feature that concatenates RUN lines ending in a trailing \ >> >> I'm

On Sun, Dec 8, 2013 at 2:11 AM, Alp Toker <alp at nuanti.com> wrote: > I'd like to propose deprecating and shortly thereafter removing the lit > test runner feature that concatenates RUN lines ending in a trailing \ > I'm really opposed to this. Especially for the Clang test suite where run lines are often *very* long and hard to organize, read, and edit without this

So after I updated all my gems, I started getting: /Library/Ruby/Gems/1.8/gems/activesupport-2.3.4/lib/active_support/ dependencies.rb:105:in `const_missing'': uninitialized constant Test::Unit::TestResult::TestResultFailureSupport (NameError) from /Library/Ruby/Gems/1.8/gems/test-unit-2.0.3/lib/test/unit/ testresult.rb:28 from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in