[Akonadi] [Bug 340614] assertion failure in KIMAP::ImapInterval::setBegin

[RJVB]

https://bugs.kde.org/show_bug.cgi?id=340614

RJVB <rjvbertin at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dvratil at redhat.com

--- Comment #2 from RJVB <rjvbertin at gmail.com> ---
I don't even understand why the ASSERT is active, because I don't build in
debug mode ...

Anyway, directly upstream of the failing assert is this:

``` C++
        //Prepare next chunk
        m_searchUidIntervall.setBegin(lastUidToSearch + 1);
        //Or are we already done?
        if (m_searchUidIntervall.begin() > m_searchUidIntervall.end()) {
```

where m_searchUidIntervall (with double l???) is the ImapInterval class where
things go wrong.
I think that the "or are we already done" test can never be true (the condition
wouldn't pass the assert and ::end returns 0xFFFFFFFF if no end has been
defined). But if it should be possible, then the assert is wrong.

However, ImapInterval::setBegin is unchanged from kdepimlibs 4.13.3 so I'm at a
loss.

As a side note: 0xFFFFFFFF is NOT the maximum value an ImapInterval::Id
(qint64) can reach ... (and for a signed int 0x7FFFFFF should have been used)
!!

-- 
You are receiving this mail because:
You are on the CC list for the bug.