# mysqlbinlog segfault on 5.1.61-rel113.2-log

**URL:** <https://forums.percona.com/t/mysqlbinlog-segfault-on-5-1-61-rel113-2-log/1780>\
**Category:** Other MySQL® Questions\
**Created:** [March 18, 2012, 7:39am UTC](https://forums.percona.com/t/mysqlbinlog-segfault-on-5-1-61-rel113-2-log/1780 "2012-03-18T07:39:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Infin1ty](https://avatars.discourse-cdn.com/v4/letter/i/ecae2f/32.png) [@Infin1ty](https://forums.percona.com/u/Infin1ty)\
**Post date:** [March 18, 2012, 7:39am UTC](https://forums.percona.com/t/mysqlbinlog-segfault-on-5-1-61-rel113-2-log/1780/1 "2012-03-18T07:39:29Z")

</div>

It’s a normal situation where one want to decode the binlog to understand in case a replication failed.  
normally one would do:  
$ mysqlbinlog --verbose --base64-output=DECODE-ROWS \>   
For some reason, starting with v5.1.60 it segfault.  
If i use the binary of mysqlbinlog from 5.1.59 it works.  
I have tried to run it both on rhel 5.7 and rhel 6.2, both segfault.

[Percona-Server-5.1.61-rel13.2-430.Linux.x86\_64/bin]# ldd mysqlbinlog  
linux-vdso.so.1 =\> (0x00007fff59ffc000)  
libpthread.so.0 =\> /lib64/libpthread.so.0 (0x0000003e21800000)  
libmysqlclient.so.16 =\> /usr/lib64/libmysqlclient.so.16 (0x0000003631200000)  
libcrypt.so.1 =\> /lib64/libcrypt.so.1 (0x0000003e23000000)  
libnsl.so.1 =\> /lib64/libnsl.so.1 (0x0000003e23400000)  
libm.so.6 =\> /lib64/libm.so.6 (0x0000003e21c00000)  
libz.so.1 =\> /usr/lib64/libz.so.1 (0x0000003e22400000)  
librt.so.1 =\> /lib64/librt.so.1 (0x0000003e22c00000)  
libc.so.6 =\> /lib64/libc.so.6 (0x0000003e21000000)  
/lib64/ld-linux-x86-64.so.2 (0x0000003e20c00000)

[Percona-Server-5.1.59-rel13.0-325.Linux.x86\_64/bin]# ldd mysqlbinlog  
linux-vdso.so.1 =\> (0x00007fff8e8e6000)  
libpthread.so.0 =\> /lib64/libpthread.so.0 (0x0000003e21800000)  
libmysqlclient.so.16 =\> /usr/lib64/libmysqlclient.so.16 (0x0000003631200000)  
librt.so.1 =\> /lib64/librt.so.1 (0x0000003e22c00000)  
libcrypt.so.1 =\> /lib64/libcrypt.so.1 (0x0000003e23000000)  
libnsl.so.1 =\> /lib64/libnsl.so.1 (0x0000003e23400000)  
libm.so.6 =\> /lib64/libm.so.6 (0x0000003e21c00000)  
libz.so.1 =\> /usr/lib64/libz.so.1 (0x0000003e22400000)  
libc.so.6 =\> /lib64/libc.so.6 (0x0000003e21000000)  
/lib64/ld-linux-x86-64.so.2 (0x0000003e20c00000)

---

<div class="post-metadata">

**Author:** ![xaprb](https://avatars.discourse-cdn.com/v4/letter/x/49beb7/32.png) [@xaprb](https://forums.percona.com/u/xaprb)\
**Post date:** [March 18, 2012, 12:06pm UTC](https://forums.percona.com/t/mysqlbinlog-segfault-on-5-1-61-rel113-2-log/1780/2 "2012-03-18T12:06:06Z")

</div>

Is this specific to Percona Server’s distribution or does it happen with standard MySQL too?

---

<div class="post-metadata">

**Author:** ![Infin1ty](https://avatars.discourse-cdn.com/v4/letter/i/ecae2f/32.png) [@Infin1ty](https://forums.percona.com/u/Infin1ty)\
**Post date:** [March 20, 2012, 1:54pm UTC](https://forums.percona.com/t/mysqlbinlog-segfault-on-5-1-61-rel113-2-log/1780/3 "2012-03-20T13:54:04Z")

</div>

I haven’t tried yet, is there a way to get the binaries as you can with percona?