Displaying 20 results from an estimated 400 matches similar to: "Core dump during UID Search"
2018 Nov 22
2
Core dump during UID Search
Op 22-11-2018 om 3:47 schreef Bert JW Regeer:
> It happened again:
> I really wish I could get some better backtrace information, but unfortunately this is it :-(
Did you install the debug symbols for Dovecot? On Debian, those are
available as a separate dovecot-dbg package. I'm not sure how FreeBSD
provides this.
Regards,
Stephan.
>
>> On Nov 15, 2018, at 17:17, Bert JW
2018 Nov 22
1
Core dump during UID Search
I?m using the package available from the quarterly repository.
I will build from ports and report back.
Bert
> On Nov 22, 2018, at 05:14, Larry Rosenman <larryrtx at gmail.com> wrote:
>
> I'm the dovecot maintainer for FreeBSD. To get DEBUG symbols, if you are building your own package, add:
>
> WITH_DEBUG_PORTS=mail/dovecot
>
> To your /etc/make.conf, and
2018 Nov 22
0
Core dump during UID Search
It happened again:
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was
2018 Nov 22
0
Core dump during UID Search
I'm the dovecot maintainer for FreeBSD. To get DEBUG symbols, if you are building your own package, add:
WITH_DEBUG_PORTS=mail/dovecot
To your /etc/make.conf, and the symbols should then be available.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: larryrtx at gmail.com
US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106
2020 Apr 06
2
Panic due to assertion failure
Hey all,
I continue to receive the following messages every so often:
dovecot[93817]: imap(xistence at 0x58.com)<39982><>: Panic: file mail-storage.c: line 2122 (mailbox_get_open_status): assertion failed: (box->opened)
dovecot[93817]: imap(xistence at 0x58.com)<39982><>: Fatal: master: service(imap): child 39982 killed with signal 6 (core not dumped -
2006 Jan 30
1
nearly there
Hi Timo et all.
At last I found with unix socket wouldn't connect and it works now.
However after auth, imap crashes with signal 6.
This happens on 1 machine, the other (unixware too) work fine.
The stack trace doesn't make much sense
here it is anway...
Core image of imap (process p1) created
CORE FILE [makedev in cmd-status.c@sys/mkdev.h]
SIGNALED 8 (fpe code[FPE_INTDIV]
2009 Aug 11
1
dovecot-1.2.3 (managesieve) crash with backtrace
>From the log:
Aug 11 09:07:23 postamt dovecot: IMAP(zensy): Panic: file mail-index-transaction-view.c: line 106 (tview_apply_flag_updates): assertion failed: (map->hdr.record_size <= tview->record_size)
Aug 11 09:07:23 postamt dovecot: IMAP(zensy): Raw backtrace: imap [0x80f0411] -> imap [0x80f0482] -> imap [0x80efe29] -> imap
[0x80c839b] -> imap [0x80cea95] -> imap
2020 Apr 06
0
Panic due to assertion failure
> On 06/04/2020 09:26 Bert JW Regeer <xistence at 0x58.com> wrote:
>
>
> Hey all,
>
> I continue to receive the following messages every so often:
>
> dovecot[93817]: imap(xistence at 0x58.com)<39982><>: Panic: file mail-storage.c: line 2122 (mailbox_get_open_status): assertion failed: (box->opened)
> dovecot[93817]: imap(xistence at
2004 Sep 21
3
Dovecot 1.0-test45 indexing issues
We're currently on dovecot 0.99.10 with a few modifications (including one
very nasty hack for the blank line at the beginning of the mailbox bug).
We're using mbox all around.
Everything works smoothly but we still ocasionally get corrupt mailboxes
and indexes that need to be wiped out.
I setup 1.0-test45 on one of our mailservers to start testing it and ran
into a few issues. The
2013 Nov 14
10
Render to clear textbox
There has to be a better way to do this. What I am trying is not working,
and seems convoluted. Essentially, a controller method is called, and exits
by rendering a partial the purpose of which is to simply clear a textbox in
the view. So I am calling the partial which established the textbox -- but
it doesn''t work (i.e. it doesn''t clear the textbox). Does anyone know of a
2007 Aug 09
8
Dtrace - Segmentation Fault
After building and bfu''in the lastest ON build, any time I run a dtrace script I get a Seg Fault. Is there a dtrace for dtrace :)
Doug
root at prae> dtrace -n ''syscall::open*:entry { printf("%s %s",execname,copyinstr(arg0)); }''
Segmentation Fault (core dumped)
root at prae> pstack core
core ''core'' of 101364: dtrace -n
2020 Feb 03
2
ASAN not finding any bugs?
Hello,
I am building sanitizers for our different platforms and trying to use
it in an example program, but while it seems like ASAN is running it's
init functions (see stdout below with ASAN_OPTIONS=verbosity=1) it
never catches anything in the program. This is LLVM 8.0.1 btw.
I was using this small test case:
int main(int argc, char** argv) {
int *array = new int[100];
delete []
2020 Feb 03
2
ASAN not finding any bugs?
Hello Alex,
Thanks for the hint. It was actually not the -O flag that created the
problem. But it pointed me in the right direction, when I passed
-fno-experimental-new-pass-manager it started to show the error. My
guess is that the new pass manager is more aggressive in removing UB?
Thanks,
Tobias
On Mon, Feb 3, 2020 at 5:29 PM Alex Brachet-Mialot
<alexbrachetmialot at gmail.com> wrote:
2013 Feb 24
1
Problem with the command hooks api
I have been trying to use the command hook api in an experimental plugin I
have written. The hook is registered using the command_hook_register function,
and for most commands my hook functions get called once as expected.
But when the client uses one of the "UID" commands (e.g. "UID FETCH" ) the
hook functions are executed twice.
I am using dovecot version 2.1.12.
Am I
2008 Sep 23
2
(not quite) reproducible segfaults in 3.0.3
In debian bug #498083 (http://bugs.debian.org/498083) someone is getting
segfaults reasonably consistently, however when using -vvvv it doesn't
happen...
Fortunately Sven was able to get a good backtrace. I can't quite see
what's causing the problem; it does seem to be related to xattrs.
Please see the bugs report at the url above for the details.
Any help much appreciated.
Paul
2007 Dec 17
3
maildir_uidlist_create assertion failure
I've been getting the following error fairly often, which tends to
result in a corrupted dovecot-uidlist.
dovecot: IMAP(example at example.com): file maildir-uidlist.c: line 1009
(maildir_uidlist_recreate): assertion failed: (file_size ==
(uoff_t)st.st_size)
dovecot: IMAP(example at example.com): Raw backtrace: imap [0x80cb740] ->
imap [0x80cb64a] -> imap [0x8070e58] -> imap(maildir
2007 Nov 23
1
MacOSX 10.4.11 update breaks tests/lapack.R (R 2.6.0)? (PR#10454)
Hello,
It seems the recent Mac OS X 10.4.11 update installed a new
libBLAS.dylib in the Accelerate framework which either contains a bug
itself or exposes a bug somewhere in R's lapack code on the PowerPC G4
and G5.
My build of R 2.6.0 executed the tests/lapack.R code succesfully when
I upgraded when 2.6.0 was released. After the OS update, it now
crashes. This happens both with the version I
2005 May 16
2
Assertion Failure in mbox-sync.c
I've been getting a few of these errors on a couple different mboxes.
This is using the CVS version as of May 14.
So far, these are the only errors and it looks like most/all of the older
ones are gone. (maybe I shouldn't say that ;-)
dovecot: May 16 17:41:07 Error: 20973 IMAP(todd.bluegenesis.com): file mbox-sync.c: line 1165 (mbox_sync_handle_eof_updates): assertion failed:
2018 Aug 30
4
crash problem when using IndirectBrInst to replace BranchInst
Hello all,
I have written a pass, which replaces condition branchinst using
indirectBr to obfuscate program.
The origin IR is as the following:
br i1 %1, label %2, label %3
And the transformed IR is as the follwoing:
%4 = select i1 %1, i8* blockaddress(@func, %2), i8* blockaddress(@func,
%3)
indirectbr i8* %4, [label %2, label %3]
The pass's core function is as the
2009 Jul 14
2
Index cache file problems in Dovecot 1.2.0
I've been seeing lots of index cache file errors (using mbox on Solaris
8 sparc 64-bit, but with 32-bit Dovecot) since I switched my account to
Dovecot 1.2.0 (we're still on 1.0.15 mostly, but I'm hoping to upgrade
to 1.1.17+ this summer, or 1.2.x if it's stable enough).
e.g.
Error: Corrupted index cache file
<path>/.imap/INBOX/dovecot.index.cache: field index too large (47