On Fri, Oct 4, 2013 at 3:01 PM, Stephan Beal <sgb...@googlemail.com> wrote:
> i'm also working on a repro in a 32-bit vm in parallel. "In theory" a
> malloc failure is not possible because fossil_malloc() aborts on alloc
> error, but we do have a few places which use malloc()/free() instead of
> fossil_{malloc,free}().
>
Update: we've got the broken manifest now (off-list) and have found the
problem (malformed/empty P-card) but don't yet know why. Jan and i are
playing with it.
@Devs: anyone touched P-card generation lately?
...
F xr.css 35f07555a0420a382004217172b613bd38a3a3f4
P
R e7fa81c6d596b4d5bf77ffdeb62d71ba
U ron
...
the only commit which can legally have a empty P-card is the initial commit
(or one without a parent, but i think that's only possible on the first
commit?).
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
