From: "Nate Jenkins" <nate@uniwest.com>
To: linux-c-programming@vger.kernel.org
Subject: Re: "double free or corruption" - how to solve this?
Date: Fri, 12 May 2006 14:06:52 -0700 [thread overview]
Message-ID: <002801c67607$fdc5dfd0$8001a8c0@NATE> (raw)
In-Reply-To: 6a00c8d50605120145r3319e9c6hdb15c3630aeffadd@mail.gmail.com
>> Hello Shriramana,
>>
>>
>> On Fri, 12 May 2006 13:41:12 +0530 "Shriramana Sharma"
>> <samjnaa@gmail.com> 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â„¢
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-05-12 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 8:11 "double free or corruption" - how to solve this? Shriramana Sharma
2006-05-12 8:19 ` wwp
2006-05-12 8:45 ` Steve Graegert
2006-05-12 21:06 ` Nate Jenkins [this message]
2006-05-12 21:35 ` Steve Graegert
2006-05-12 21:46 ` Nate Jenkins
2006-05-12 12:01 ` james-lists
2006-05-12 21:53 ` Steve Graegert
-- strict thread matches above, loose matches on Subject: below --
2006-05-12 20:40 AW: " Jedenastik, Günther
2006-05-12 22:18 ` Steve Graegert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002801c67607$fdc5dfd0$8001a8c0@NATE' \
--to=nate@uniwest.com \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.