mysql core dump

Hi,

First off I apologize if this is a repost since it appears my original
post was lost in transmission...

Anyway, I currently running a load test on my application and I'm
seeing a pretty consistent core dump from mysql. My application
simply reads from the database (using the mysql odbc APIs) of 80000+
records while at the same time it is being updated by another
application pretty frequently. Below is the stack trace that I keep
seeing. I'm not sure if there's something here that I'm doing wrong
as far as the usage of the odbc APIs. Has anyone seen this similar
core before? If so, any possible reason for this?

#0 0x001217a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
(gdb) where
#0 0x001217a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x001617a5 in raise () from /lib/tls/libc.so.6
#2 0x00163209 in abort () from /lib/tls/libc.so.6
#3 0x0019571a in __libc_message () from /lib/tls/libc.so.6
#4 0x0019bfbf in _int_free () from /lib/tls/libc.so.6
#5 0x0019c33a in free () from /lib/tls/libc.so.6
#6 0x005675c4 in my_no_flags_free () from /usr/lib/mysql/
libmysqlclient.so.10
#7 0x0056a92d in free_root () from /usr/lib/mysql/libmysqlclient.so.
10
#8 0x00562353 in ?? () from /usr/lib/mysql/libmysqlclient.so.10
#9 0x0a932e30 in ?? ()
#10 0x00000000 in ?? ()

Here's the mysql rpms that is installed in my box:

mysqlclient10-3.23.58-4.RHEL4.1
mysql-server-4.1.20-1.RHEL4.1
mysql-4.1.20-1.RHEL4.1
mysql-devel-4.1.20-1.RHEL4.1

Thanks.

Avalon

Never mind...silly me....I found my problem....your classic invalid
write to a memory space error (thank you valgrind!)

On May 16, 2:43 pm, Avalon1178 <Avalon1...@aol.com> wrote:
> Hi,
>
> First off I apologize if this is a repost since it appears my original
> post was lost in transmission...
>
> Anyway, I currently running a load test on my application and I'm
> seeing a pretty consistent core dump from mysql. My application
> simply reads from the database (using the mysql odbc APIs) of 80000+
> records while at the same time it is being updated by another
> application pretty frequently. Below is the stack trace that I keep
> seeing. I'm not sure if there's something here that I'm doing wrong
> as far as the usage of the odbc APIs. Has anyone seen this similar
> core before? If so, any possible reason for this?
>
> #0 0x001217a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> (gdb) where
> #0 0x001217a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> #1 0x001617a5 in raise () from /lib/tls/libc.so.6
> #2 0x00163209 in abort () from /lib/tls/libc.so.6
> #3 0x0019571a in __libc_message () from /lib/tls/libc.so.6
> #4 0x0019bfbf in _int_free () from /lib/tls/libc.so.6
> #5 0x0019c33a in free () from /lib/tls/libc.so.6
> #6 0x005675c4 in my_no_flags_free () from /usr/lib/mysql/
> libmysqlclient.so.10
> #7 0x0056a92d in free_root () from /usr/lib/mysql/libmysqlclient.so.
> 10
> #8 0x00562353 in ?? () from /usr/lib/mysql/libmysqlclient.so.10
> #9 0x0a932e30 in ?? ()
> #10 0x00000000 in ?? ()
>
> Here's the mysql rpms that is installed in my box:
>
> mysqlclient10-3.23.58-4.RHEL4.1
> mysql-server-4.1.20-1.RHEL4.1
> mysql-4.1.20-1.RHEL4.1
> mysql-devel-4.1.20-1.RHEL4.1
>
> Thanks.
>
> Avalon