Crash in libmysqlclient_r
Posted by: Chris White
Date: March 18, 2012 01:57PM

Has anybody seen the following crash when using libmysqlclient_r.16.0.0 when running multiple threads to insert/update/delete items from the DB.

#0 0xffffe410 in __kernel_vsyscall ()
(gdb) where
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb78458d0 in raise () from /lib/
#2 0xb7846ff3 in abort () from /lib/
#3 0xb787b32b in __libc_message () from /lib/
#4 0xb7880cb1 in malloc_printerr () from /lib/
#5 0xb7882314 in free () from /lib/
#6 0xb66ad78d in my_free (ptr=0xb0002e38)
at /export/home/pb2/build/sb_0-2629600-1291401802.22/mysqlcom-pro-5.5.8/mysys/my_malloc.c:128
#7 0xb66a46b6 in vio_delete (vio=0x2)
at /export/home/pb2/build/sb_0-2629600-1291401802.22/mysqlcom-pro-5.5.8/vio/vio.c:276
#8 0xb668bdb7 in end_server (mysql=0xb00015d4)
at /export/home/pb2/build/sb_0-2629600-1291401802.22/mysqlcom-pro-5.5.8/sql-common/client.c:1098
#9 0xb668c0c0 in cli_safe_read (mysql=0xb00015d4)
at /export/home/pb2/build/sb_0-2629600-1291401802.22/mysqlcom-pro-5.5.8/sql-common/client.c:750
#10 0xb668c3df in cli_read_rows (mysql=0xb00015d4, mysql_fields=0x0, fields=7)
at /export/home/pb2/build/sb_0-2629600-1291401802.22/mysqlcom-pro-5.5.8/sql-common/client.c:1563
#11 0xb668c86b in cli_read_query_result (mysql=0xb00015d4)
at /export/home/pb2/build/sb_0-2629600-1291401802.22/mysqlcom-pro-5.5.8/sql-common/client.c:3793
#12 0xb6689cb4 in mysql_real_query (mysql=0xb00015d4,
query=0xab808c98 "SELECT * FROM schedule_time_block WHERE `schedule_group_name_id` = 10788", length=72)
at /export/home/pb2/build/sb_0-2629600-1291401802.22/mysqlcom-pro-5.5.8/sql-common/client.c:3829
#13 0xb69f0ed4 in mysqlpp::DBDriver::execute (this=0xb00015d0,
qstr=0xab808c98 "SELECT * FROM schedule_time_block WHERE `schedule_group_name_id` = 10788", length=72)
at lib/dbdriver.h:288
#14 0xb69ecd62 in mysqlpp::Query::use (this=0xaeb759e4,
str=0xab808c98 "SELECT * FROM schedule_time_block WHERE `schedule_group_name_id` = 10788", len=72)
at lib/query.cpp:669
#15 0xb69ed013 in mysqlpp::Query::use (this=0xaeb759e4, s=@0xaeb759a0) at lib/query.cpp:652
#16 0xb70f5b98 in mysqlpp::Query::storein_sequence<std::vector<ScheduleTimeBlockDTO, std::allocator<ScheduleTimeBlockDTO> > > (this=0xaeb759e4, con=@0xaeb75c4c, s=@0xaeb759a0)
at /media0/7.0-now/server/CommonLib/include/mysql++/query.h:756
#17 0xb70f5e01 in mysqlpp::Query::storein<ScheduleTimeBlockDTO> (this=0xaeb759e4, con=@0xaeb75c4c,
s=@0xaeb759a0) at /media0/7.0-now/server/CommonLib/include/mysql++/query.h:901
#18 0xb70f5e6d in mysqlpp::Query::storein<std::vector<ScheduleTimeBlockDTO, std::allocator<ScheduleTimeBlockDTO> > > (this=0xaeb759e4, con=@0xaeb75c4c) at /media0/7.0-now/server/CommonLib/include/mysql++/query.h:882
#19 0xb70f603b in getMultiple<ScheduleTimeBlockDTO, std::vector<bool, std::allocator<bool> >*> (
object=@0xaeb75b64, connIn=0xaeb75c3c, typeIn=0xaeb75ba0) at dbInterface.hxx:379

It seems to be happening when I am runing more than 10 threads all accessint\g the DB a the same time.

Any help would be helpful


Options: ReplyQuote

Written By
Crash in libmysqlclient_r
March 18, 2012 01:57PM
March 18, 2012 02:41PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.