Bug #40040 Invalid read in mysql_stmt_fetch_column() when fetching several rows with blobs
Submitted: 15 Oct 2008 10:01 Modified: 15 Nov 2008 11:12
Reporter: Sebastien FLAESCH Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: C API (client library) Severity:S2 (Serious)
Version:5.1.28 OS:Linux (libc 2.3)
Assigned to: CPU Architecture:Any
Tags: blobs fetch mysql_stmt_fetch_column memory read

[15 Oct 2008 10:01] Sebastien FLAESCH
Description:
When fetching multiple rows with BLOB values by using the function:
    mysql_stmt_fetch_column()
valgrind reports an invalid read in libmysqlclient.so:

==12155== Invalid read of size 8
==12155==    at 0x44EA488: (within /opt3/dbs/mys/5.1.28/lib/libmysqlclient.so.16.0.0)
==12155==    by 0x44A707D: fetch_result_with_conversion (libmysql.c:4044)
==12155==    by 0x44A67BA: mysql_stmt_fetch_column (libmysql.c:4662)
==12155==  Address 0x40d1988 is 0 bytes after a block of size 43,624 alloc'd
==12155==    at 0x4004825: malloc (vg_replace_malloc.c:207)
==12155==    by 0x44AD36D: my_malloc (my_malloc.c:34)

Tested with version 5.1.28, seems to be solved in 6.0.4, but should be fixed in 5.1.x ...

How to repeat:
We need to provide a test program in C to reproduce, where can we send this?
[15 Oct 2008 11:00] Sebastien FLAESCH
We don't get the valgrind error report with a MySQL 5.0.13 client.
[15 Oct 2008 11:12] MySQL Verification Team
Please re-open this bug report when the test case is provided. Thanks in advance.
[16 Nov 2008 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".