List:MySQL++« Previous MessageNext Message » Date:May 4 2007 6:30pm
Subject:Re: query memory bug
View as plain text  
Valgrind really helped me track down the problem. Which was with the 
structure its self.

Just had to check and make sure there wasn't something weird with the query.


Warren Young wrote:
> aberger@stripped wrote:
>> if I print out the structure before I create the query object, the 
>> structure looks fine. When i print out the structure after the query 
>> object a small section of the data in the structure is corrupt. If I 
>> remove the mysql++ calls from the function the struct remains fine.
> When you remove those calls, you are changing the memory layout of 
> your program.  You can't disentangle that fact from the possibility 
> that MySQL++ is corrupting your program's memory without more tests.  
> I suggest running the MySQL++-free version of your program under a 
> heap checking tool such as Valgrind.
query memory bugaberger@agsense.net3 May
  • Re: query memory bugWarren Young3 May
    • Re: query memory bugaberger@agsense.net4 May