List:MySQL++« Previous MessageNext Message »
From:Jan Busch Date:December 20 2005 7:45pm
Subject:Re: Crashes and memory corruption
View as plain text  
I have had got the same problems, the same gdb-backtraces, and I think 
it's inside the ResUse-deconstructor.
It calls purge() which contains:

"*delete* names_;
names_ = 0;
*
delete* types_;
types_ = 0;"

The problem is, that "names_" and "types_" are not neccessayrily 
initialized with "new".

Since I changed the code like this:

"		*if* (names_)
		{
			*delete* names_;
			names_ = 0;
		}

		*if* (types_)
		{
			*delete* types_;
			types_ = 0;
		}

", everything works perfect.

Thread
Crashes and memory corruptionBjörn Persson16 Aug
  • Re: Crashes and memory corruptionWarren Young16 Aug
    • Re: Crashes and memory corruptionBjörn Persson17 Aug
      • Re: Crashes and memory corruptionWarren Young17 Aug
        • Re: Crashes and memory corruptionBjörn Persson18 Aug
          • Re: Crashes and memory corruptionThomas Werth18 Aug
          • Re: Crashes and memory corruptionWarren Young18 Aug
        • Re: Crashes and memory corruptionBjörn Persson25 Nov
          • Re: Crashes and memory corruptionWarren Young15 Dec
            • Re: Crashes and memory corruptionBjörn Persson15 Dec
Re: Crashes and memory corruptionJan Busch20 Dec
  • Re: Crashes and memory corruptionChris Frey20 Dec
Re: Crashes and memory corruptionJan Busch21 Dec