Hello.
I'm new in this Forum. I'm not usually ask to any one to help me. But I'm trying to solve this problem for a week, and I've could not solve it.
I don't need someone solve my mistake, I only need to know how to find it.
My project has so many files and so many libraries. So it's not possible to paste here. I've not have idea where is my bug.
I'm programing in C++ using eclipse indigo and compiling with g++.
In runtime I get that error. But the program closes and I cannot backtrace to find who cause that error.
I've tried to use try{} catch{} to try to catch the exception, but it doesn't works. Never catches an exception.
I think the error is inside the VLC library. But if I run that portion of code alone it works fine. So surely I have an overflow on my program causing that problem in VLC library.
Any one knows how to get working try{} catch{}?
Any one knows if it's possible to find the variable causing the problem with the info gave in the error message? (double free or corruption (out): 0x0000000006143d00)
Thanks in advance.

you can try to use valgrind to catch memory related problems.

1 members found this post helpful.

Try running it through valgrind to get a start:

1 members found this post helpful.

I hope that you are using git for version-control, even on "your own personal" project, because this will give you the opportunity to definitively see ... "what changed recently?" And, to see exactly what each and every change consisted of.

Most probably, there's a point in time at which "you thought that the program worked," and another point in time at which "you noticed the bug." Take a look at the most-recent changes.

A few other tips, all of which go back to "coding discipline" ...

• Always allocate storage blocks with calloc or some other means of initializing every block to known all-zeros.
• When you deallocate something, immediately in the next statement set all associated pointers to NULL.
• Write test-scripts to independently exercise all major pieces of the program in isolation to the others. Run these tests all the time to catch regressions.
• Use debugging-tools that add "eyecatchers" around storage-blocks to detect "off-by-one" overwrites and other similar problems. Consider leaving them in in the production(!) code.

1 members found this post helpful.

I like to use Electric Fence in cases like this:

(or similiar)

under lucky constellations it will stop much earlier -- making debugging easier

1 members found this post helpful.

Thanks a lot for your quick responses.
They has been very helpfull to me.
Now I'm debugging my program. I'm correcting many mistakes.
It is not 100% corrected but now I'm on the right way.
Thanks again.