← Back to team overview

enterprise-support team mailing list archive

[Bug 1466023] [NEW] Segmentation fault on debian wheezy and mydumper 0.9

 

Public bug reported:

I created a dump using mydumper.
When I try to import the data to another database using myloader I get segmentation fault.
 
Gdb tells me the following:

(gdb) thread apply all bt

Thread 2 (Thread 0x7f486bc8b700 (LWP 31616)):
#0  0x00007f486db4653c in recv () from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x00007f486ddb833b in vio_read () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18
#2  0x00007f486ddb83b2 in vio_read_buff () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18
#3  0x00007f486dd9b3c6 in ?? () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18
#4  0x00007f486dd9b64f in ?? () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18
#5  0x00007f486dd9beb9 in my_net_read () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18
#6  0x00007f486dd9253a in cli_safe_read () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18
#7  0x00007f486dd93925 in ?? () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18
#8  0x00007f486dd952f6 in mysql_real_query () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18
#9  0x0000000000402e0b in restore_data (conn=conn@entry=0x19fe000, database=0x1a0ff00 "mab", table=0x1a10a00 "placements", filename=0x19fc740 "mab.placements.sql.gz",
    is_schema=is_schema@entry=0, need_use=need_use@entry=1) at /home/maticm/mydumper/myloader.c:485
#10 0x00000000004031b1 in process_queue (td=0x19fc820) at /home/maticm/mydumper/myloader.c:429
#11 0x00007f486d007f45 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007f486db3eb50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#13 0x00007f486c8ac95d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#14 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f486e516720 (LWP 31615)):
#0  0x00007f486c809042 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x0000000000402a1b in add_table (filename=<optimized out>, conf=0x7fff5d700260) at /home/maticm/mydumper/myloader.c:388
#2  0x000000000040380b in restore_databases (conf=conf@entry=0x7fff5d700260, conn=conn@entry=0x19e0030) at /home/maticm/mydumper/myloader.c:217
#3  0x00000000004025f9 in main (argc=1, argv=0x7fff5d700398) at /home/maticm/mydumper/myloader.c:162


I am using version 0.9 from checked out from launchpad. If you sense there's a line mismatch it's because I've added a couple of g_message()'s into the code since I'm debugging this and I forgot to locate and remove them. The function calls are there though..

** Affects: mydumper
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1466023

Title:
  Segmentation fault on debian wheezy and mydumper 0.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/mydumper/+bug/1466023/+subscriptions


Follow ups

References