MySQL Forums :: C/C++ :: libmysqlclient crashing

Hello all.

Got a strange one and am baffled. I have a server that delivers updates to the network and uses MySQL as a backend database engine.

Up until about a week ago, the server was working perfectly. However, it has started crashing when it tries to make the connection to the MySQL server.

The crash is triggered by an assertion failure within malloc in libc. The message I get is

UpdServer: malloc.c:3091: sYSMALLOc: Assertion `(old_top == (((mbinptr) (((char *) &((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct malloc_chunk, fd)))) && old_size == 0) || ((unsigned long) (old_size) >= (unsigned long)((((__builtin_offsetof (struct malloc_chunk, fd_nextsize))+((2 * (sizeof(size_t))) - 1)) & ~((2 * (sizeof(size_t))) - 1))) && ((old_top)->size & 0x1) && ((unsigned long)old_end & pagemask) == 0)' failed.

Stack trace shows

#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb66208df in raise () from /lib/libc.so.6
#2  0xb6622220 in abort () from /lib/libc.so.6
#3  0xb6663040 in __malloc_assert () from /lib/libc.so.6
#4  0xb66650c8 in _int_malloc () from /lib/libc.so.6
#5  0xb666759a in malloc () from /lib/libc.so.6
#6  0xb7627eec in my_once_alloc () from /usr/lib/libmysqlclient.so.16
#7  0xb762839c in ?? () from /usr/lib/libmysqlclient.so.16
#8  0xb7628d3a in ?? () from /usr/lib/libmysqlclient.so.16
#9  0xb7629348 in get_charset_by_csname () from /usr/lib/libmysqlclient.so.16
#10 0xb76497f0 in mysql_init_character_set () from /usr/lib/libmysqlclient.so.16
#11 0xb764a0c2 in mysql_real_connect () from /usr/lib/libmysqlclient.so.16
#12 0x0804ac64 in OpenMysql (MyPid=9809, Server=0x804d428 "localhost", User=0x804d41f "AAAA", 
    Password=0x804d414 "BBBB", Database=0x804d40c "Voodoo") at UpdServer.c:956
#13 0x0804bd7c in ProcessConnection (Connection=0x8051d30) at UpdServer.c:701
#14 0x0804c130 in main (argc=1, argv=0xbfe4dac4) at UpdServer.c:58

The version of libclientmysql I have installed is 5.1.57-0.3.1

The actual memory in the box passes the bios memory check - no errors but could this be a problem with the hardware?

Any clues gratefully received.

Cheers - AK