Jemalloc library is hitting Segmentation fault on CentOS-7

[Roel Van de Paar]

Hi Jason,

Please let us know how you went. Thanks

On Fri, Sep 9, 2016 at 2:46 AM, Jason Evans <jasone at canonware.com> wrote:

> Hi Ramesh,
>
> This crash is happening inside glibc, perhaps due to recursive allocation
> failing despite a temporary bootstrap allocation environment having been
> set up inside jemalloc.  Are you able to determine whether something is
> going wrong during a malloc() (or similar) call inside get_nprocs()?
>
> I'm in the process of setting up a CentOS 7 system right now, but it will
> take some time before I can reproduce this.
>
> Thanks,
> Jason
>
> > On Aug 25, 2016, at 2:27 AM, Ramesh Sivaraman <
> ramesh.sivaraman at percona.com> wrote:
> >
> > Hi Team,
> >
> > Forgot to mention version details
> >
> > jemalloc.x86_64  : 3.6.0-3.el7
> >
> > On Thu, Aug 25, 2016 at 2:49 PM, Ramesh Sivaraman <
> ramesh.sivaraman at percona.com> wrote:
> > Hi Team,
> >
> > Jemalloc library is hitting  Segmentation fault on CentOS-7
> >
> > With debug library Segmentation fault issue triggering with simple `ls`
> command.
> >
> > $ export LD_PRELOAD=/usr/lib/debug/usr/lib64/libjemalloc.so.1.debug
> > $ ls
> > Segmentation fault (core dumped)
> > $
> >
> > Also seeing a segmentation fault issue (same issue?) with non-debug
> jemalloc
> >
> > $ export LD_PRELOAD=/usr/lib64/libjemalloc.so.1
> > $ ./bin/mysqld --version
> > Segmentation fault (core dumped)
> > $ gdb ./bin/mysqld core.11345.mysqld.11
> > [..]
> > (gdb) bt
> > +bt
> > #0  0x00007f1c21fa5964 in get_nprocs () from /lib64/libc.so.6
> > #1  0x00007f1c21f70b0c in sysconf () from /lib64/libc.so.6
> > #2  0x00007f1c26efebd0 in malloc_ncpus () at src/jemalloc.c:256
> > #3  malloc_init_hard () at src/jemalloc.c:776
> > #4  0x00007f1c26f01705 in malloc_init () at src/jemalloc.c:292
> > #5  calloc (num=1, size=32) at src/jemalloc.c:1123
> > #6  0x00007f1c22eb1690 in _dlerror_run () from /lib64/libdl.so.2
> > #7  0x00007f1c22eb1198 in dlsym () from /lib64/libdl.so.2
> > #8  0x00007f1c23f88fec in ?? () from /lib64/libasan.so.0
> > #9  0x00007f1c23f7b2c9 in ?? () from /lib64/libasan.so.0
> > #10 0x00007f1c23f7d91b in __asan_init_v1 () from /lib64/libasan.so.0
> > #11 0x00007f1c271426c3 in _dl_init_internal () from
> /lib64/ld-linux-x86-64.so.2
> > #12 0x00007f1c2713445a in _dl_start_user () from
> /lib64/ld-linux-x86-64.so.2
> > #13 0x0000000000000002 in ?? ()
> > #14 0x00007fff9d552740 in ?? ()
> > #15 0x00007fff9d55274d in ?? ()
> > #16 0x0000000000000000 in ?? ()
> > (gdb)
> >
> > --
> > Best Regards,
> >
> > Ramesh
> >
> >
> >
> >
> >
> > --
> > Best Regards,
> >
> > Ramesh Sivaraman
> > QA Engineer, Percona
> > http://www.percona.com/
> > Phone : +91 8606432991
> > Skype : rameshvs02
> >
> >
> > _______________________________________________
> > jemalloc-discuss mailing list
> > jemalloc-discuss at canonware.com
> > http://www.canonware.com/mailman/listinfo/jemalloc-discuss
>
> _______________________________________________
> jemalloc-discuss mailing list
> jemalloc-discuss at canonware.com
> http://www.canonware.com/mailman/listinfo/jemalloc-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jemalloc.net/mailman/jemalloc-discuss/attachments/20160914/fb67b878/attachment.html>