Re: [PATCH 2/2] python: annotate all calls into libnotmuch with types

Subject:Re: [PATCH 2/2] python: annotate all calls into libnotmuch with types

Date:Fri, 24 Jan 2014 09:17:27 -0400

To:Justus Winter ,


From:David Bremner

Justus Winter <> writes:

> Quoting Justus Winter (2011-12-07 19:49:31)

> And another one:
[stack trace snipped]
> #69 0x00000000004e10be in PyRun_SimpleFileExFlags (fp=0xb99c10, filename=<optimized out>, closeit=1, flags=0x7fffc13a1f60) at ../Python/pythonrun.c:936
> #70 0x00000000004f10fd in Py_Main (argc=<optimized out>, argv=<optimized out>) at ../Modules/main.c:599
> #71 0x00007f72f2cbaead in __libc_start_main (main=<optimized out>, argc=<optimized out>, ubp_av=<optimized out>, init=<optimized out>, fini=<optimized out>, 
>     rtld_fini=<optimized out>, stack_end=0x7fffc13a2078) at libc-start.c:228
> #72 0x000000000041f199 in _start ()
> (gdb) q
> with stderr saying:
> terminate called after throwing an instance of 'Xapian::DatabaseModifiedError'
> Aborted (core dumped)
> This is an uncought c++ exception, right? If so I think it has to be
> cought somewhere in libnotmuch and turned into the appropriate error
> code (hm, there is only the generic XAPIAN_EXCEPTION, I thought there
> was a way to indicate that the db has been modified?).

Can you still reproduce this bug?  If so, a small test case (python is
fine, but ideally not requiring afew) would be helpful.