similar to: core file generation

libnbd's copy/copy-nbd-error.sh was triggering an assertion failure in nbdkit: $ nbdcopy -- [ nbdkit --exit-with-parent -v --filter=error pattern 5M error-pread-rate=0.5 ] null: ... nbdkit: pattern.2: debug: error-inject: pread count=262144 offset=4718592 nbdkit: pattern.2: debug: pattern: pread count=262144 offset=4718592 nbdkit: pattern.1: debug: error-inject: pread count=262144

Hi there, I have a problem when I try to create a new user with swat. I use binaries of Samba 2.2.2 coming from www.samba.org, or from www.sunfreeware.com on Solaris 2.6 and on 8. I compiled the sources and the result is the same. When I click on "Add New User" (Server Password Management), I receive a nearly blank page: I can only see the samba gif on top and the user is not

Samba: binary kit from samba.org Samba version: 2.0.6 computer: SGI indigo2 with a 250MHz 4400 CPU, 64MB RAM, Irix 6.5.6m me: tarjei.jensen@kvaerner.com It looks like every time smbd spawns, the child process seems to die a horrible death and leave a core file. As a result I am unable to use any netbios services on the machine. The core file which I have examined says that the process died with

Hi, sorry for the double post, I stupidly composed this as a reply to an earlier mail, which causes it to appear in an older thread. Posting again so it doesn't get lost in the archives: dovecot 1.1.7 reliably crashes every time I try to open a mailbox using IMAP. Error in the logs: dovecot: Dec 02 23:14:15 Error: setmntent(/etc/mtab) failed: No such file or directory dovecot: Dec 02

Hi, I am new in the world of CentOS and Linux. I am not a computer professional but want to do work in Linux, for which I am trying to learn the Linux basics. Having a PC at home and somebody told me CentOS is a great Linux distro for stability. I am having some basic queries which are as follows: 1. I am having the PC and already installed is Fedora Core 11 as well as Windows XP (dual boot).

Hi, Has anyone any ideas what is causing my smbd processes to crash? The files being accessed via samba are on an NFS mounted directory. In the samba log file I am getting the following errors: [2004/12/03 16:31:33, 0] smbd/oplock.c:request_oplock_break(1026) request_oplock_break: no response received to oplock break request to pid 2181 9 on port 53336 for dev = 2c00002, inode = 297939333

Experts, (Now that I am able to run imap...) Here's what I am seeing with imap, it seems to die in the latest nightly. (tss, I am still trying to get dbx to work properly, maybe it won't, but I got some more details here.) ... 2 select "INBOX" * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.

On May 24, 2008, at 12:12 PM, Bill Wendling wrote: > Let us know if you would like extra eyes on the two PPC failures. Many > of us have a lot of experience with C++. :-) Do you know where these > allocations are? I don't mind if people help out, so here's some information: FAIL: /nfs/llvm/src/llvm/test/Transforms/PredicateSimplifier/ 2006-11-04-ReplacingZeros.ll Failed with

When attempting to save a message from the INBOX to a folder in a collection (like, .projects.dovecot), I get behavior like this (in GDB). Any clue what might be going wrong? Here's where a SIGABRT happens: 280 return array->buffer->used / array->element_size; This is the stack trace: (gdb) where #0 mail_index_map_get_ext_idx (map=0x1200c0db0, ext_id=0,

Hi, I'm experiencing the following problem when runnig dovecot-1.0-test set up to authenticate users against openldap, while the corresponding setup with dovecot-0.99.11 works fine : . my platform : FreeBSD 5.3-RELEASE-p1 . dovecot version : dovecot-1.0-test57 . openldap version : openldap-2.1.27 - Description : When I talk IMAP to the dovecot server, I can connect on port 143 and

OK, I've figured out which drive is bad. Before I go any further let me give a brief HD configuration explanation. The primary IDE has a 80gig(Master) HD, and an internal zip drive(Slave) connected to it. The two 200gig Hard Drives are connect to a PCI ATA controller card(Not a promise card), one is master, the other one is slave. It is the slave 200gig drive that is going bad. Now, I

On 6 July 2011 14:55, D S Khudia <daya.khudia at gmail.com> wrote: > The following is an example code generation for arm and x86 for a same IR > BB. In the x86 code I can see that the same computation is done twice and > result is stored in two different registers and then these two different > registers are used for comparision. Yes, but you shouldn't rely on it, since the

On May 24, 2008, at 4:25 PM, Marcel Moolenaar wrote: > On May 24, 2008, at 12:12 PM, Bill Wendling wrote: >> Let us know if you would like extra eyes on the two PPC failures. >> Many >> of us have a lot of experience with C++. :-) Do you know where these >> allocations are? > > I don't mind if people help out, so here's some information: Nice!

Hi, > On Fri, 2011-04-29 at 09:05 +0200, Peter J. Philipp wrote: >> You don't check for malloc failure. I've made a patch that is possibly >> wrong but it saves the program from SIGSEGV and replaces it with SIGABRT. On Fri, 29 Apr 2011, Philipp Schafft wrote: > But I have a question: > Not all of them (only had a brief look at the patch) look to be in a >

Mersenne Twister generator is known to be sensitive to the algorithm used to generate its initial state. The initialization used in R generates the initial state in a way, which leaves linear dependencies mod 2 among the bits in the initial state. Since Mersenne Twister performs only operations, which are linear mod 2, these dependencies propagate to the output sequence. An easy to see

Hi, I found what seems to be a bug in smbd (and smbclient?) from samba-2.2.8a-1. Scenario is the following: All users have accounts in linux box "mate", with homes mounted via NFS from linux box "fserver". mate and fserver run samba-2.2.8a-1, mate ONLY validates passwords and has no shares; fserver in turn, ONLY shares [homes] and [netlogon], but has no users, so samba uses

https://bugzilla.mindrot.org/show_bug.cgi?id=1548 Summary: Double free in OpenSSH clientloop.c/xmalloc.c via cmdline port forwarding Product: Portable OpenSSH Version: 5.1p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo:

Right, this gets into the whole error-handling philosophy of LLVM, or lack thereof. The idea is that so long as your frontend generating IR gives correct IR and is well-behaved, LLVM will not assert, abort, or crash. Once you've successfully debugged your frontend, you should never see this kind of error from LLVM and need to recover from it. In practice, this is true enough that it is

Any suggestions where I should look? (Is this a known problem?) bash-2.05a$ unset MAIL bash-2.05a$ /usr/libexec/dovecot/imap * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED] Logged in as admin 001 select inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen

Hi Andrea, Thanks for working on this. I can see two approaches to solving this problem. The first one (that you suggested) is to catch this pattern after register allocation. The second approach is to eliminate this redundancy during instruction selection. Can you please look into catching this pattern during iSel? The idea is that ADDSS does an ADD plus BLEND operations, and you can easily