search for: crashy

Hi everyone, the attached message does reliably crash my dovecot when trying to access a folder containing it. Crash notice in mail.log: Apr 13 17:36:12 rafter dovecot: child 23215 (imap) killed with signal 11 My `dovecot --version` says: 0.99.8 Has this problem been fixed in current dovecot? For now I have just quarantined the offending message but obviously I need to upgrade my dovecot soon

It's my vague impression that View() is workable on Windows and maybe on MacOS, but on Ubuntu Linux 9.04 (intrepid) it seems completely unstable. I can reliably crash R by trying to look at a very small, simple data frame ... I was going to try to run with debug turned on, but my installed version (2.9.0) doesn't have debugging symbols, and I'm having trouble building the latest

...two inside and two out), plus a firewall box. And the only reason there are that many is because the manufacturing system had to run on RHEL, which we don't use anywhere else. None of them ever crash. None of them ever have services just fall over and die for no good reason. I don't run crashy, undependable servers or provide crashy, undependable services. If I wanted to run crashy, undependable stuff, I'd be running MS-Win servers. If the new server can't replace the old one, on its own, running Samba4 as an AD DC, then I'll fall back to running it as a plain old workgroup...

...If you don?t want to use the HTTP API, you can use the raw doveadm protocol. > > https://wiki.dovecot.org/Design/DoveadmProtocol > > -FG Thanks, I didn't know about that. I suppose testing the HTTP API and then switching to the raw doveadm protocol over TCP if it turns out "crashy" wouldn't mean too much work. -- James Beck Andrews & Arnold Ltd Tel: 03333 400999 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <https://dovecot.org/pip...

Hi Think I tracked down why Windows suddenly went horrible crashy - the newest SWIG release generates slightly different code for object tracking, so our fixmodule.rb wasn''t picking up the broken line, so we got a nasty regression. Anyway, the patch (SVN:862) gives me a major improvement in stability Windows. Please could you let me know how SVN HEA...

...plus a firewall box. And the only reason there > are that many is because the manufacturing system had to run on RHEL, > which we don't use anywhere else. > > None of them ever crash. None of them ever have services just fall > over and die for no good reason. I don't run crashy, undependable > servers or provide crashy, undependable services. If I wanted to run > crashy, undependable stuff, I'd be running MS-Win servers. > > If the new server can't replace the old one, on its own, running Samba4 > as an AD DC, then I'll fall back to running it...

...raw doveadm protocol. >>> >>> https://wiki.dovecot.org/Design/DoveadmProtocol >>> >>> -FG >> Thanks, I didn't know about that. I suppose testing the HTTP API and >> then switching to the raw doveadm protocol over TCP if it turns out >> "crashy" wouldn't mean too much work. > Why use the HTTP API at all? How about JSON. :) Good luck, Reio

...ed --- and failed --- to generate float-heavy ARM code via the JIT on an armhf platform. No matter what I did, it would always generate armel code instead. This was on LLVM 3.2, which was all that was available then. Now I'm running into a requirement to do this again: while it's much less crashy than it was, I still can't seem to persuade the JIT to generate hard-float code. This is with LLVM 3.3, 3.4 and 3.5. I'm using MCJIT (although I've tried without, as well), and I've tried setting FloatABI to HardFloat. Does anyone know if this is actually working yet? If so, are th...

...n a predicate. Instead of compiling those compilers again, the tool downloads them from the cloud. The tool allows you to down download and run compilers, or bisect on a range of commits with a predicate. Example, find where a crash started: $ llvmlab bisect bash -c "%(path)s/bin/clang -c crashy.c” FAIL: clang-r219899-t2014-10-15_21-42-48-b809 FAIL: clang-r219778-t2014-10-15_06-18-17-b787 FAIL: clang-r219773-t2014-10-14_21-18-07-b779 FAIL: clang-r219746-t2014-10-14_17-01-07-b775 FAIL: clang-r219739-t2014-10-14_16-09-35-b771 FAIL: clang-r219729-t2014-10-14_15-21-29-b757 clang-r219719-t2014...

In trying to add wxTextCtrl to wxruby-swig, I''ve been running into a problem with the argument conversion that appears to be a SWIG director bug. It is tied to multiple inheritance, and is related to SWIG specifically making director''s ''initialize'' take a first argument, but because ''initialize'' is static there isn''t a self value

On Thu, 3 Sep 2015 15:07:37 +0100 Rowland Penny <rowlandpenny241155 at gmail.com> wrote: [snip] > > The kerberos default_realm must be the samba AD DC domain name and > usually So if I put the Samba AD DC in, say, "addc.example.com," "addc.example.com" must be the Kerberos default_realm? > the samba DNS server (internal or bind) is just the dns >

Hi, Jonas! On Tue, Nov 1, 2016 at 3:26 AM, Jonas Wagner <jonas.wagner at epfl.ch> wrote: > Hi Eugene, > > I think this is really cool! You've convinced me to try out PVS on some of > my own projects :) > > Of all the warnings presented in the article, there was one for which I > thought it's a false positive. By default, LLVM is compiled without RTTI and >

...etContext(), mdArray); >> > > If I had to hazard a guess, it's that mdArray is left with dangling > pointers to an array (initializer list) that ceases to exist once the ';' > on line 2 is reached. So when the elements the ArrayRef references are > accessed, it gets crashy. > > I'd say try writing it like: > > auto *node = MDTuple::get(M.getContext(), {ConstantInt::get(Int64Ty, 0), > newMD}); > > Also try testing with ASan or MSan, perhaps? > > >> >> Thus far, I have been developing on a version of Clang with debugging >&...

...s an HP d530 SFF workstation (model DG784A) with 4GiB of RAM. It has run for years on the lenny xen + linux stack. If my notes are correct, it also ran smoothly for about a year with the lenny hypervisor + kernel and the squeeze userland. Rebooting into squeeze xen + linux makes the machine very crashy. The dom0 kernel often crashes, and the xen hypervisor also crashes. This is a report of a hypervisor crash (i have not been able to reproduce it, because the machine does not actually reboot in 5 seconds as claimed, and physical access to hard-reset the box is more time-consuming than i'd li...

Hello, I am editing the LowerTypeTests pass in LLVM, and part of my additions include the following 3 lines of code: // newTypeName is a std::string MDString* newMD = MDString::get(M.getContext(), newTypeName); ArrayRef<Metadata*> mdArray {ConstantInt::get(Int64Ty, 0), newMD}; auto* node = MDTuple::get(M.getContext(), mdArray); Thus far, I have been developing on a version of Clang with

...the windows-pr library, such as Windows::COM::Automation, Windows::Error, etc. I can add anything that''s missing. Advantages include: * No compiler required * Easier to debug * A potentially better and more flexible interface * The current WIN32OLE library is still occasionally buggy and crashy The major pain point is that this is a 6200+ line source file. :( Any takers? Regards, Dan This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have recei...

...PI, you can use the raw doveadm protocol. >> >> https://wiki.dovecot.org/Design/DoveadmProtocol >> >> -FG > > Thanks, I didn't know about that. I suppose testing the HTTP API and > then switching to the raw doveadm protocol over TCP if it turns out > "crashy" wouldn't mean too much work. Why use the HTTP API at all? I guess it helps integrators who don?t have direct socket access, but doveadm is much lighter than HTTP and so should always be more performant .. and it should be more stable as well. (We connect via local socket, which will al...

...>> >>>> https://wiki.dovecot.org/Design/DoveadmProtocol >>>> >>>> -FG >>> Thanks, I didn't know about that. I suppose testing the HTTP API and >>> then switching to the raw doveadm protocol over TCP if it turns out >>> "crashy" wouldn't mean too much work. >> Why use the HTTP API at all? > > How about JSON. :) JSON and HTTP headers do make it easy to get started, but they?re inefficient compared to doveadm. JSON in particular limits us to UTF-8 text, so any application that needs to send non-UTF-8...

...hat i know > of) seem to use Core Audio. So they all freak out if i try to play a 24/96 > file. Without even worrying about your 24/96 issue, which OSX flac player have you been using? Here's what I've tried, and why it doesn't work well for me: - the old MacAmp player - very crashy - xmms - works, even with coreaudio output (xmms-coreaudio plugin, make sure to apply the patch that tells OS X that it's a realtime thread). however, i have a second sound card (usb griffin iMic) that's hooked to the stereo, i'd like music to go there and system audio to...

I think this is the minimal recipe: winetricks ie6 winetricks ie8 wine iexplore Installing ie6 just makes the menus work, I think.