Hi Robert, On 7 Aug., 09:06, Robert Bradshaw <rober...@math.washington.edu> wrote: ... > > I came to asking about "sage -gdb" since sage's last words at crashing > > suggest to use "sage -gdb". But then I would expect that it is > > explained in detail in the documentation. However, searching "sage - > > gdb" in the developer's guide or reference manual yields nothing. > > Start it up with sage -gdb. Hitting ctl-C will dump you into the > debugger. From there just google around for gdb documentation--sage- > gdb is just running sage under gdb.
Thank you! This was the bit of information I was missing: How can I get the gdb prompt, so that I can insert break points and those things. Meanwhile I found that the memory which caused the crash when freeing it was allocated, and then re-allocated by realloc: 1. Allocate enough memory to do some computation in that block of memory, and 2. since the result of that computation will, in general, be smaller than that block, do a re-allocation, so that now only the size of the result is allocated. It realloc error prone? Disclaimer: It isn't my code. But I link against it, so it is my problem... Cheers, Simon --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
