"Jason A. Donenfeld" writes:
> As discussed on IRC, notmuch segfaults with 1.3.1 but not with 1.2.5 on
> notmuch-new:
>
Ahem. Years later, and notmuch works OK with xapian 1.3.4, so I think we
can consider this bug closed.
d
___
Olly wrote on IRC:
> bremner: ok, 1.2 explicitly no-oped skip_to() on an iterator at_end on
> trunk that code has been rewritten without that explicit check, and
> the iterator internals are NULL then i think restoring the check is
> reasonable, though I'm not sure if we actually promise that's
Olly wrote on IRC:
bremner: ok, 1.2 explicitly no-oped skip_to() on an iterator at_end on
trunk that code has been rewritten without that explicit check, and
the iterator internals are NULL then i think restoring the check is
reasonable, though I'm not sure if we actually promise that's
David Bremner writes:
>
> I managed to duplicate this problem on Debian testing by rebuilding
> Olly's packages (https://launchpad.net/~ojwb/+archive/xapian-1.3) for
> sid and running the following script in the ./test subdirectory
Olly wrote on IRC:
> bremner: ok, 1.2 explicitly no-oped
"Jason A. Donenfeld" writes:
> As discussed on IRC, notmuch segfaults with 1.3.1 but not with 1.2.5 on
> notmuch-new:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x775a5367 in Xapian::TermIterator::skip_to(std::string const&) ()
> from /usr/lib64/libxapian-1.3.so.1
> (gdb)
As discussed on IRC, notmuch segfaults with 1.3.1 but not with 1.2.5 on
notmuch-new:
Program received signal SIGSEGV, Segmentation fault.
0x775a5367 in Xapian::TermIterator::skip_to(std::string const&) ()
from /usr/lib64/libxapian-1.3.so.1
(gdb) bt
#0 0x775a5367 in
Jason A. Donenfeld ja...@zx2c4.com writes:
As discussed on IRC, notmuch segfaults with 1.3.1 but not with 1.2.5 on
notmuch-new:
Program received signal SIGSEGV, Segmentation fault.
0x775a5367 in Xapian::TermIterator::skip_to(std::string const) ()
from /usr/lib64/libxapian-1.3.so.1