I was able to reproduce this bug on Fedora 19, x86_64.
Reproduction required a slight modification of the recipe: the breakpoint in malloc.c needs to happen at line 3865. This line will continue to change as new versions of the library are released.
[testuser@localhost ~]$ cat gdb_script
break main
r
set scheduler-locking on
break 54
break 59
break 60
c
break malloc.c:3865
c
thread 2
c
c
thread 1
c
[testuser@localhost ~]$
I was able to reproduce this bug on Fedora 19, x86_64.
Reproduction required a slight modification of the recipe: the breakpoint in malloc.c needs to happen at line 3865. This line will continue to change as new versions of the library are released.
Required packages: glibc-debuginfo boost-devel boost-thread gcc-c++
[testuser@localhost ~]$ yum info glibc debuginfo, langpacks, refresh-packagekit
Loaded plugins: auto-update-
Installed Packages
Name : glibc
Arch : x86_64
Version : 2.17
Release : 18.fc19
[testuser@localhost ~]$ cat /etc/redhat-release
Fedora release 19 (Schrödinger’s Cat)
[testuser@localhost ~]$ cat gdb_script
break main
r
set scheduler-locking on
break 54
break 59
break 60
c
break malloc.c:3865
c
thread 2
c
c
thread 1
c
[testuser@localhost ~]$