Bug #1089
invalid pointer in "free"
Description
I have a non-trivial program written using CoCoALib which causes the following error (on Fedora Linux):
*** Error in `./BigGCD-factor': free(): invalid pointer: 0x0000000001ef2bc8 ***
The problem appears after about 54 hours' CPU, and seems not to occur with small parameters (and faster run times).
A second run reproduced the same problem at the same point (as far as I recall).
History
#1 Updated by John Abbott almost 7 years ago
- Subject changed from inavlid pointer in "free" to invalid pointer in "free"
How to debug this? Finding a smaller/faster example would help... but how?
Perhaps I'll try running it with valgrind
or maybe gdb?
It'll take a long time, I fear.
UPDATE With valgrind
I estimate more than 1500 hours' run-time; so I have stopped it. Trying gdb
instead...
#2 Updated by John Abbott almost 7 years ago
- Status changed from New to In Progress
- Assignee set to John Abbott
- % Done changed from 0 to 10
After about 150 hours the program running under gdb the program finally died from a SIGABRT
.
The problem occurred inside DistrMPolyImplPP::ourDeleteSummands
; apparently a coefficient pointer is invalid (corrupted?)
#3 Updated by John Abbott about 1 month ago
- Related to Feature #743: Better errors: give supplementary info about the error added
#4 Updated by John Abbott about 1 month ago
- Related to deleted (Feature #743: Better errors: give supplementary info about the error)