Hello!
Zbigniew Zagórski wrote:
Hi!
Danny MacMillan pisze:
Hi,
I just got an error using monotone. What I did was basically follow the
<cut>
> Revision: 045b0286268ed071e6ac83bc87cdcb751b38718f
<cut>
> C:\Program Files\monotone\mtn.exe: fatal: memory access violation
> this is almost certainly a bug in monotone.
> please send this error message, the output of 'C:\Program
>Files\monotone\mtn.exe version --full',
> and a description of what you were doing to monotone-devel@nongnu.org
<cut>
Thanks for report! This error is reproducible on other machines. I am
analyzing the cause.
Failing test case (on nvm workspace):
mtn log --from 045b0286268ed071e6ac83bc87cdcb751b38718f
fails also here, but in somewhat different place (maybe it's a buffering
problem?):
Hello!
OK, problem identified. Someone/somewhere had misconfigured machine (?)
and thus generated weird date cert:
$ mtn ls certs cdf1680ec496d22f863184a
<cut>
Key : tbrow...@gmail.com (475055ec71...)
Sig : ok
Name : date
Value : 1969-12-25T17:04:08
^^^^^^^^^^^^^^^^^^^
and looks like localtime on woe32 can't cope with this - thus returning
0 from localtime call.
Recap: failing test case:
$ mtn log --from cdf1680ec496d22f863184a --last 1
--
Zbigniew Zagórski
/ software developer / geek / http://zbigg.blogspot.com /
_______________________________________________
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
