enterprise-support team mailing list archive

[icesyc <icesyc@xxxxxxxxx>]

Public bug reported:

the core dump info

Core was generated by `mydumper -r 100000 -u xxxxx -p xxxxxxx  -h xxxxxxxx -c -e -o /data1/db'.
Program terminated with signal 11, Segmentation fault.
#0  0x00002af4e1393d7a in ____strtoull_l_internal () from /lib64/libc.so.6
(gdb) where
#0  0x00002af4e1393d7a in ____strtoull_l_internal () from /lib64/libc.so.6
#1  0x000000000040628f in dump_database (conn=<value optimized out>, database=0x54aa98 "bk_audit")
    at /data1/mydumper-0.6.1/mydumper.c:1410
#2  0x0000000000406fb5 in start_dump (conn=0x511e50) at /data1/mydumper-0.6.1/mydumper.c:1018
#3  0x000000000040785d in main (argc=1, argv=0x7fffca1a9588) at /data1/mydumper-0.6.1/mydumper.c:748
(gdb) quit

** 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/1332506

Title:
  mydumper segment fault

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