Quoth Sebastian Spaeth on Jun 20 at 9:29 am:
> On Sun, 19 Jun 2011 19:51:11 -0400, Austin Clements
> wrote:
> > A double will precisely represent integers up to 2^53, so this
> > conversion shouldn't be a problem until the year 285422109 or so.
>
> But given that it works, is it actually
On Sun, 19 Jun 2011 19:51:11 -0400, Austin Clements wrote:
> A double will precisely represent integers up to 2^53, so this
> conversion shouldn't be a problem until the year 285422109 or so.
But given that it works, is it actually necessary, that xapian
apparently pulls an int from the
Quoth Sebastian Spaeth on Jun 20 at 9:29 am:
On Sun, 19 Jun 2011 19:51:11 -0400, Austin Clements amdra...@mit.edu wrote:
A double will precisely represent integers up to 2^53, so this
conversion shouldn't be a problem until the year 285422109 or so.
But given that it works, is it actually
On Sun, Jun 19, 2011 at 5:45 AM, Dmitry Kurochkin
wrote:
> Hi Sebastian, Patrick.
>
> On Sat, 18 Jun 2011 12:30:01 +0200, Sebastian Spaeth SSpaeth.de> wrote:
>> On Fri, 17 Jun 2011 17:10:24 +0100, Patrick Totzke :
>> > #0 ?0x006eb87d in Xapian::Document::Internal::get_value(unsigned int)
>> >
On Sun, 19 Jun 2011 13:45:07 +0400, Dmitry Kurochkin wrote:
> Sebastian, are you able to reproduce the issue? A python script that
> triggers the bug, perhaps? I would look at this if I can reproduce the
> problem.
No, not reproducable at all. I only had it twice actually. Patrick had it
Hi Sebastian, Patrick.
On Sat, 18 Jun 2011 12:30:01 +0200, Sebastian Spaeth
wrote:
> On Fri, 17 Jun 2011 17:10:24 +0100, Patrick Totzke :
> > #0 0x006eb87d in Xapian::Document::Internal::get_value(unsigned int) const
> > () from /usr/lib/sse2/libxapian.so.22
> > #1 0x006eb952 in
Hi Sebastian, Patrick.
On Sat, 18 Jun 2011 12:30:01 +0200, Sebastian Spaeth sebast...@sspaeth.de
wrote:
On Fri, 17 Jun 2011 17:10:24 +0100, Patrick Totzke :
#0 0x006eb87d in Xapian::Document::Internal::get_value(unsigned int) const
() from /usr/lib/sse2/libxapian.so.22
#1 0x006eb952 in
On Sun, 19 Jun 2011 13:45:07 +0400, Dmitry Kurochkin wrote:
Sebastian, are you able to reproduce the issue? A python script that
triggers the bug, perhaps? I would look at this if I can reproduce the
problem.
No, not reproducable at all. I only had it twice actually. Patrick had it
several
On Sun, Jun 19, 2011 at 5:45 AM, Dmitry Kurochkin
dmitry.kuroch...@gmail.com wrote:
Hi Sebastian, Patrick.
On Sat, 18 Jun 2011 12:30:01 +0200, Sebastian Spaeth sebast...@sspaeth.de
wrote:
On Fri, 17 Jun 2011 17:10:24 +0100, Patrick Totzke :
#0 0x006eb87d in
On Fri, 17 Jun 2011 17:10:24 +0100, Patrick Totzke :
> #0 0x006eb87d in Xapian::Document::Internal::get_value(unsigned int) const
> () from /usr/lib/sse2/libxapian.so.22
> #1 0x006eb952 in Xapian::Document::get_value(unsigned int) const () from
> /usr/lib/sse2/libxapian.so.22
> #2 0x00523963
On Fri, 17 Jun 2011 17:10:24 +0100, Patrick Totzke :
#0 0x006eb87d in Xapian::Document::Internal::get_value(unsigned int) const
() from /usr/lib/sse2/libxapian.so.22
#1 0x006eb952 in Xapian::Document::get_value(unsigned int) const () from
/usr/lib/sse2/libxapian.so.22
#2 0x00523963 in
Thanks to amdragon's hint on how to get a stacktrace, here it is.
I startet gdb --args python, imported my stuff and ran it directly.
I can't really interpret this, but it seems as if its libxapians fault
doesn't it?
best,
/p
(gdb) bt
#0 0x006eb87d in
On Thu, 16 Jun 2011 22:54:39 +0100, Patrick Totzke wrote:
> Unfortunately, as it segfaults, I don't get a stacktrace here.
> The line that seems to cause the segfault is this one:
> https://github.com/pazz/notmuch-gui/blob/master/alot/db.py#L181
Just some followup. get_date() calls libnotmuch's:
On Thu, 16 Jun 2011 22:54:39 +0100, Patrick Totzke wrote:
Unfortunately, as it segfaults, I don't get a stacktrace here.
The line that seems to cause the segfault is this one:
https://github.com/pazz/notmuch-gui/blob/master/alot/db.py#L181
Just some followup. get_date() calls libnotmuch's:
Thanks to amdragon's hint on how to get a stacktrace, here it is.
I startet gdb --args python, imported my stuff and ran it directly.
I can't really interpret this, but it seems as if its libxapians fault
doesn't it?
best,
/p
(gdb) bt
#0 0x006eb87d in
Hi all!
First off: Thanks Sebastian for your recent work on the python bindings.
It all makes a little bit more sense now without the __len__ and all.
As some of you might have read on the IRC channel, I'm facing really
strange behaviour with Message.get_date() which unfortunately,
I cannot
Hi all!
First off: Thanks Sebastian for your recent work on the python bindings.
It all makes a little bit more sense now without the __len__ and all.
As some of you might have read on the IRC channel, I'm facing really
strange behaviour with Message.get_date() which unfortunately,
I cannot
17 matches
Mail list logo
