enterprise-support team mailing list archive

[Paul Williamson <paul.williamson@xxxxxxxxxxxxxx>]

Public bug reported:

I am getting a segfault on Centos 5.6 (Final), compiled against very old
non-Percona 5.0:

mydumper --version
mydumper 0.6.1, built against MySQL 5.0.95

uname -r
2.6.18-238.12.1.el5

Valgrind output:

==18481== Memcheck, a memory error detector
==18481== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==18481== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==18481== Command: mydumper --database=XXX --host=localhost --user=XXX --password=XXX --outputdir=XXX --rows=500000 --compress --build-empty-files --threads=4 --compress-protocol
==18481==
==18481== Invalid read of size 1
==18481== at 0x387E87C0FC: strcasecmp (in /lib64/libc-2.5.so)
==18481== by 0x4067AE: start_dump (mydumper.c:914)
==18481== by 0x4074C9: main (mydumper.c:748)
==18481== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==18481==
==18481==
==18481== Process terminating with default action of signal 11 (SIGSEGV)
==18481== Access not within mapped region at address 0x0
==18481== at 0x387E87C0FC: strcasecmp (in /lib64/libc-2.5.so)
==18481== by 0x4067AE: start_dump (mydumper.c:914)
==18481== by 0x4074C9: main (mydumper.c:748)
==18481== If you believe this happened as a result of a stack
==18481== overflow in your program's main thread (unlikely but
==18481== possible), you can try to increase the size of the
==18481== main thread stack using the --main-stacksize= flag.
==18481== The main thread stack size used in this run was 10485760.
==18481==
==18481== HEAP SUMMARY:
==18481== in use at exit: 102,774 bytes in 182 blocks
==18481== total heap usage: 314 allocs, 132 frees, 178,320 bytes allocated
==18481==
==18481== LEAK SUMMARY:
==18481== definitely lost: 216 bytes in 1 blocks
==18481== indirectly lost: 16,416 bytes in 3 blocks
==18481== possibly lost: 41,772 bytes in 97 blocks
==18481== still reachable: 44,370 bytes in 81 blocks
==18481== suppressed: 0 bytes in 0 blocks
==18481== Rerun with --leak-check=full to see details of leaked memory
==18481==
==18481== For counts of detected and suppressed errors, rerun with: -v
==18481== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 4 from 4)
Segmentation fault

I'm sure it's probably caused by very old MySQL with very new mydumper,
but any help you can give would be great. This is an older suite of
servers that are getting phased out. I am also using mydumper on Ubuntu
12.04 with no problems. Would still like to get this working though.

Let me know if you need any more info.

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

Title:
  Seg fault: Centos 5.6, mydumper 0.6.1, mysql 5.0

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