monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-devel] FPE (divide by zero?) with db info --full on new repo


From: Jack Lloyd
Subject: [Monotone-devel] FPE (divide by zero?) with db info --full on new repo
Date: Thu, 22 Oct 2009 14:46:19 -0400
User-agent: Mutt/1.5.20 (2009-06-14)

~$ mkdir test

~$ cd test/

~/test$ mtn -d test.mtn db init

~/test$ mtn -d test.mtn setup . -b net.randombit.test

~/test$ touch 1

~/test$ mtn add 1
mtn: adding 1 to workspace manifest

~/test$ mtn ci . -m "test"
mtn: beginning commit on branch 'net.randombit.test'
mtn: committed revision 266b0d7f4c639becf7435be02ed697720f9e306f

~/test$ mtn db info --full
mtn: fatal signal: Floating point exception
this is almost certainly a bug in monotone.
please send this error message, the output of 'mtn version --full',
and a description of what you were doing to address@hidden
do not send a core dump, but if you have one,
please preserve it in case we ask you for information from it.
Floating point exception

~/test$ mtn version --full
monotone 0.45 (base revision: a19f8b2017c81c3c6c8b2bb3247f865f6ed4e5a9)
Running on          : Linux 2.6.29-gentoo-r5-3 #4 SMP Fri Jul 24 19:12:01 EDT 
2009 x86_64
C++ compiler        : GNU C++ version 4.4.1
C++ standard library: GNU libstdc++ version 20090722
Boost version       : 1_39
SQLite version      : 3.6.17 (compiled against 3.6.16)
Lua version         : Lua 5.1
PCRE version        : 7.9 2009-04-11 (compiled against 7.9)
Botan version       : 1.8.7 (compiled against 1.8.7)
Changes since base revision:
format_version "1"

new_manifest [a4583b2d0cae8cb6889b8701543aeb4efc7e1554]

old_revision [a19f8b2017c81c3c6c8b2bb3247f865f6ed4e5a9]

  Generated from data cached in the distribution;
  further changes may have been made.

No debugging info (this mtn is my /usr/bin one via Gentoo portage) so
I couldn't get a backtrace, and I'm not feeling like dealing with
building nvm head right at the moment so someone else can do it or
eventually I'll get to it.

Obvious guess: division by zero in computing the percentiles.
some_timestamp / (# checkins - 1) or suchlike.

After second checkin, no problem.

-Jack




reply via email to

[Prev in Thread] Current Thread [Next in Thread]