Code Forums - View Single Post

MealMan401 · 04-10-2005, 08:58 PM

OK, I see what you are saying about keeping track of how many times that piece of code runs, and the implications of it not being correct.

But the thing that I am confused about is the specific message that I got in the console. Usually if you try to delete something that you don't own then you simply get the message "Segmentation fault". But the message was " *** glibc detected *** free(): invalid pointer: 0x0804ee70 *** Aborted " for the attempted deletion of a edge (which is just a struct). And " *** glibc detected *** double free or corruption (!prev): 0x0804fa70 ***
Aborted for the attempted deletion of the array.

I googled for a while trying to find a clear explanation of what those error messages were, but to no avail.

04-10-2005, 08:58 PM	#6 (permalink)
MealMan401 Registered User Join Date: Apr 2004 Posts: 10	OK, I see what you are saying about keeping track of how many times that piece of code runs, and the implications of it not being correct. But the thing that I am confused about is the specific message that I got in the console. Usually if you try to delete something that you don't own then you simply get the message "Segmentation fault". But the message was " * glibc detected * free(): invalid pointer: 0x0804ee70 * Aborted " for the attempted deletion of a edge (which is just a struct). And " * glibc detected * double free or corruption (!prev): 0x0804fa70 * Aborted for the attempted deletion of the array. I googled for a while trying to find a clear explanation of what those error messages were, but to no avail.