[Bugs] [Bug 1359131] Glusterd crashes upon receiving SIGUSR1

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1359131



--- Comment #5 from Pavel Malyshev <p.malishev at gmail.com> ---
Atin,

Thank you for the quick reply!
This is a release build without debug symbols.
I've attached coredump.
The backtrace for the crashed thread is:
(gdb) bt
#0  0x00007f591bfde943 in _IO_vfprintf_internal (s=s at entry=0x7f59196d01d0,
format=<optimized out>, format at entry=0x7f591cc6aa10 "%s.%s - usage-type %s
memusage", 
    ap=ap at entry=0x7f59196d1398) at vfprintf.c:1661
#1  0x00007f591c09c165 in ___vsnprintf_chk (s=0x7f59196d0362
"mgmt/glusterd.management - usage-type ", maxlen=<optimized out>, flags=1,
slen=<optimized out>, 
    format=0x7f591cc6aa10 "%s.%s - usage-type %s memusage",
args=0x7f59196d1398) at vsnprintf_chk.c:63
#2  0x00007f591cbf98a9 in gf_proc_dump_add_section_fd () from
/usr/lib/x86_64-linux-gnu/libglusterfs.so.0
#3  0x00007f591cbf9ab5 in gf_proc_dump_add_section () from
/usr/lib/x86_64-linux-gnu/libglusterfs.so.0
#4  0x00007f591cbf9e3e in ?? () from
/usr/lib/x86_64-linux-gnu/libglusterfs.so.0
#5  0x00007f591cbfa658 in gf_proc_dump_xlator_info () from
/usr/lib/x86_64-linux-gnu/libglusterfs.so.0
#6  0x00007f591cbfad00 in gf_proc_dump_info () from
/usr/lib/x86_64-linux-gnu/libglusterfs.so.0
#7  0x0000560afcb5dbae in glusterfs_sigwaiter ()
#8  0x00007f591c360184 in start_thread (arg=0x7f59196d7700) at
pthread_create.c:312
#9  0x00007f591c08d37d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

List of threads:
(gdb) info threads
  Id   Target Id         Frame 
  7    Thread 0x7f59152df700 (LWP 12079) pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  6    Thread 0x7f5919ed8700 (LWP 11999) 0x00007f591c367b9d in nanosleep () at
../sysdeps/unix/syscall-template.S:81
  5    Thread 0x7f5914ade700 (LWP 12080) 0x00007f591c08da13 in epoll_wait () at
../sysdeps/unix/syscall-template.S:81
  4    Thread 0x7f59186d5700 (LWP 12002) pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
  3    Thread 0x7f591d0a4780 (LWP 11998) 0x00007f591c36165b in pthread_join
(threadid=140020575758080, thread_return=0x0) at pthread_join.c:92
  2    Thread 0x7f5918ed6700 (LWP 12001) pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
* 1    Thread 0x7f59196d7700 (LWP 12000) 0x00007f591bfde943 in
_IO_vfprintf_internal (s=s at entry=0x7f59196d01d0, format=<optimized out>, 
    format at entry=0x7f591cc6aa10 "%s.%s - usage-type %s memusage",
ap=ap at entry=0x7f59196d1398) at vfprintf.c:1661

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.