On Fri, Oct 4, 2013 at 3:00 PM, Jan Nijtmans <jan.nijtm...@gmail.com> wrote:
> Noting that both Stephan and I tried it on a 64-bit machine with a lot
> of memory, could this be an unchecked memory overflow somewhere?
>
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}().
--
----- 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
