Hello Shriramana,
On Fri, 12 May 2006 13:41:12 +0530 "Shriramana Sharma"
<samjnaa@xxxxxxxxx> wrote:
> One of my programs, which was working quite well till now, suddenly
> gives me the error:
>
> *** glibc detected *** double free or corruption (top): 0x0808a338 ***
> Aborted
>
> It is a pure C program compiled with GCC 4.02 -- I do not understand
> why it does not work suddenly. Please tell me what the above error can
> be.
Would be nice to run it from gdb, in order to get the backtrace when it
crashes. This should help you understand where and why :).
Additionally, you can try valgrind, which reports typical programming
errors like calling free() twice on the same object.
\Steve
-
Steve,
I just saw that utility the other day. It looks interesting. How do you
typically use it? or grindcall-grindval? Do you know of a good tutorial
you could point me/us to?
TIA,
N8™
-
: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
