Uf ... Thank you so much Ellie, now it works fine.
Right now I was fighting against my rusty gdb knowledge, although I had almost
defeated him ;)
Cheers,
Carlos
El 17/06/2019 a las 2:44, ellie timoney escribió:
Hi Carlos,
Sudden overnight intuition, and I think this will fix the issue --
Hi Carlos,
Sudden overnight intuition, and I think this will fix the issue -- the problem
isn't that the lseek is failing at >2GB; the problem is that its off_t return
value is being truncated to an int before being checked to see if it's negative
for the error case (so any "I succeeded, the of
Hi Carlos,
This is quite weird, I'm not sure why a 64bit platform would have any trouble
around the 2GB mark??
What does the Cyrus ./configure report for your system's integer sizes? e.g.
mine shows:
> checking size of int... 4
> checking size of long... 8
> checking size of size_t... 8
> c
Hi Ellie,
Thanks for answering. We use latest 64bit Oracle Linux (not CentOs like I said
before, sorry) and zlib is also 64bit version:
# uname -a
Linux xxx 3.10.0-957.12.2.el7.x86_64 #1 SMP Tue May 14 17:35:45 PDT 2019
x86_64 x86_64 x86_64 GNU/Linux
# yum list installed zlib
L
It kinda sounds like your platform might be 32bit? Or your zlib is compiled to
use 32bit integer sizes?
On Mon, Jun 3, 2019, at 10:07 PM, Carlos Larrañaga wrote:
> Hi,
>
> We're testing backup feature un cyrus-imapd 3.0.10. There's no problem when
> backup is created first time, but when the ba
