Looking for some clues as to what this might mean.
ps. is there a way to turn the backtrace OFF?
Looking for some clues as to what this might mean.
ps. is there a way to turn the backtrace OFF?
Last edited by MK27; 09-05-2008 at 03:00 PM.
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
munmap is where "free" ends up, so munmap_chunk is part of "free" (or delete if you use C++). So my guess would be that you are trying to free something that isn't a valid pointer [or some other allocation overwrote the end of its memory and clobbered the next bit of memory that is the part that describes the memory you are trying to free].
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
You mean because it takes up so much history in your terminal and you can't see what happened before the backtrace?ps. is there a way to turn the backtrace OFF?
Not that I know of. However, I'd imagine the backtrace is dumped to stderr. So if your program doesn't use stderr, you could redirect it to /dev/null (or the equivalent for your operating system).
dwk
Seek and ye shall find. quaere et invenies.
"Simplicity does not precede complexity, but follows it." -- Alan Perlis
"Testing can only prove the presence of bugs, not their absence." -- Edsger Dijkstra
"The only real mistake is the one from which we learn nothing." -- John Powell
Other boards: DaniWeb, TPS
Unofficial Wiki FAQ: cpwiki.sf.net
My website: http://dwks.theprogrammingsite.com/
Projects: codeform, xuni, atlantis, nort, etc.