Re: [Monotone-devel] crash when pulling the monotone source from the venge.net repository

[Ali Asad Lotia]

So on my second attempt to pull from the venge.net server, here is  
what happened:

et-g4-pb:~/rcs lotia$ mtn --db=mtn.db pull venge.net  
"net.venge.monotone*"
mtn: setting default server to venge.net
mtn: setting default branch include pattern to 'net.venge.monotone*'
mtn: setting default branch exclude pattern to ''
mtn: doing anonymous pull; use -kKEYNAME if you need authentication
mtn: connecting to venge.net
mtn: first time connecting to server venge.net
mtn: I'll assume it's really them, but you might want to double-check
mtn: their key's fingerprint: 70a0f283898a18815a83df37c902e5f1492e9aa2
mtn: warning: saving public key for address@hidden to database
mtn: finding items to synchronize:
mtn: bytes in | bytes out | certs in | revs in
mtn:   23.3 k |       633 |        0 |       0
mtn: bytes in | bytes out |    certs in |   revs in
mtn:   23.9 M |       633 |  6305/30621 | 1606/7662
mtn: fatal: std::logic_error: database.cc:1314: invariant 'I(final ==  
ident)' violated
mtn: this is almost certainly a bug in monotone.
mtn: please send this error message, the output of 'mtn --full-version',
mtn: and a description of what you were doing to monotone- 
address@hidden
mtn: wrote debugging log to /Users/lotia/.monotone/dump
mtn: if reporting a bug, please include this file

so the answer to your report is yes.

I have attached the dump file again and additionally have the output  
of make check attached as well.

Hope this helps you,
Ali

dump0924
Description: Binary data

checkoutput
Description: Binary data

On Sep 23, 2006, at 3:45 AM, Nathaniel Smith wrote:

> On Fri, Sep 22, 2006 at 12:54:16AM -0400, Ali Asad Lotia wrote:
> > et-g4-pb:~/rcs lotia$ mtn --db=mtn.db pull venge.net
> > "net.venge.monotone*"
> [...]
> > mtn: bytes in | bytes out |    certs in |   revs in
> > mtn:   43.8 M |       633 | 21190/30529 | 5318/7639
> > mtn: fatal: std::logic_error: database.cc:1314: invariant 'I(final ==
> > ident)' violated
>
> Thanks for the report!  If you run the command again, do you have the
> same problem? I was suspecting a possible bug in the file
> reconstruction logic that got rewritten for 0.30, but I just wrote
> ~2000 random test cases for that and it seems fine... and when I try
> reproducing this by running the same command with the 0.30 release,
> that works for me too.
>
> It's _possible_ that it's, say, a hardware issue with your machine --
> if your memory decided to flip a bit at the wrong time, you could get
> that error.  But it might be a bit early to assume that.
>
> Did you run the testsuite on your build?  Did it pass?  ("make check"
> in your build directory.)
>
> -- Nathaniel
>
> --  
> "...All of this suggests that if we wished to find a modern-day model
> for British and American speech of the late eighteenth century, we  
> could
> probably do no better than Yosemite Sam."
>
> !DSPAM:4514e60e211146614514141!