List:Falcon Storage Engine« Previous MessageNext Message »
From:Olav Sandstaa Date:October 20 2008 12:09pm
Subject:Re: [Fwd: Valgrind warning in Falcon code.]
View as plain text  
Hakan Kuecuekyilmaz wrote:
> Vlad, Kevin,
>
> maybe you have an idea why we get this Valgrind warning?
>   

I do not know why Valgrind is complaing here. To me it seems like it is 
the C++ runtime library that do the allocation? The code was checked in 
as part of bug #39260 "Falcon should detect that it has been compiled 
without support for C++ exception" in the following commit:

  http://lists.mysql.com/commits/53693

This code should also run in the pushbuild test on the falcon tree. I do 
not think there has been any reports from Pushbuild about this in the 
Falcon tree?

Olav

>
> -------- Forwarded Message --------
>   
>> From: Rafal Somla <Rafal.Somla@stripped>
>> To: hakan@stripped
>> Cc: Backup development list <dev-backup@stripped>
>> Subject: Valgrind warning in Falcon code.
>> Date: Mon, 20 Oct 2008 13:48:30 +0200
>>
>> Hi Hakan,
>>
>> After my last merge of 6.0-main and backup trees I see the following valgrind 
>> warning:
>>
>>     
>>> ==16219== 16 bytes in 1 blocks are still reachable in loss record 2 of 6
>>> ==16219==    at 0x4904B35: malloc (vg_replace_malloc.c:149)
>>> ==16219==    by 0x33D49B0251: __cxa_get_globals (in
> /usr/lib64/libstdc++.so.6.0.7)
>>> ==16219==    by 0x33D49AFE94: __cxa_allocate_exception (in
> /usr/lib64/libstdc++.so.6.0.7)
>>> ==16219==    by 0x8C392D: checkExceptionSupport() (ha_falcon.cpp:167)
>>> ==16219==    by 0x8C39B9: StorageInterface::falcon_init(void*)
> (ha_falcon.cpp:182)
>>> ==16219==    by 0x784E0C: ha_initialize_handlerton(st_plugin_int*)
> (handler.cc:440)
>>> ==16219==    by 0x81D9D9: plugin_initialize(st_plugin_int*)
> (sql_plugin.cc:1006)
>>> ==16219==    by 0x8234D2: plugin_init(int*, char**, int)
> (sql_plugin.cc:1213)
>>> ==16219==    by 0x68915E: init_server_components() (mysqld.cc:4093)
>>> ==16219==    by 0x68A7E6: main (mysqld.cc:4575)
>>>       
>> I get this when running several backup tests under valgrind (backup, 
>> backup_lock_myisam, backup_multi_blocks, backup_myisam1, backup_myisam2, 
>> backup_nodata_driver, backup_procedures, backup_securefilepriv, backup views). 
>> Probably this affects all tests which use Falcon engine.
>>
>> Could you bring it to the attention of the Falcon team and tell me how do you 
>> propose to deal with it.
>>
>> Rafal
>>     

Thread
[Fwd: Valgrind warning in Falcon code.]Hakan Kuecuekyilmaz20 Oct
  • Re: [Fwd: Valgrind warning in Falcon code.]Olav Sandstaa20 Oct
    • RE: [Fwd: Valgrind warning in Falcon code.]Vladislav Vaintroub20 Oct
    • Re: [Fwd: Valgrind warning in Falcon code.]Hakan Kuecuekyilmaz20 Oct
      • Re: [Fwd: Valgrind warning in Falcon code.]Olav Sandstaa20 Oct
        • Re: [Fwd: Valgrind warning in Falcon code.]Hakan Kuecuekyilmaz20 Oct