On 19 Apr., 05:33, Stephen Montgomery-Smith <step...@missouri.edu> wrote: > I think I have found the problem with sympow. It is nothing to do with > elliptic curves. It is simply a malloc/free error. > > In util.c there is a function free_data, which frees TACKS[0]. TACKS[0] > is meant to be allocated in disk.c, but there are circumstances when > TACKS[0] is not allocated. > > See the attached patch. > > I am not going to submit it as a trac ticket until I have heard from > others. In general, how to different OS's react to "free(NULL)"?
That's not directly related to the operating system, since malloc() and free() are C library functions, not system calls. ISO C specifies that free(NULL) shouldn't do anything, especially not raise an error, as already mentioned. -leif -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
