[Bugs] [Bug 1637743] Glusterd seems to be attempting to start the same brick process twice
bugzilla at redhat.com
bugzilla at redhat.com
Tue Oct 9 22:36:33 UTC 2018
https://bugzilla.redhat.com/show_bug.cgi?id=1637743
--- Comment #2 from Shyamsundar <srangana at redhat.com> ---
### Basic core pattern where symbol resolution fails ###
Test: https://build.gluster.org/job/line-coverage/530/consoleText
Thread 1 (Thread 0x7fa197877700 (LWP 25856)):
#0 x86_64_fallback_frame_state (context=0x7fa197875c70,
context=0x7fa197875c70, fs=0x7fa197875d60) at ./md-unwind-support.h:58
#1 uw_frame_state_for (context=context at entry=0x7fa197875c70,
fs=fs at entry=0x7fa197875d60) at ../../../libgcc/unwind-dw2.c:1253
#2 0x00007fa1a26a6fb9 in _Unwind_Backtrace (trace=0x7fa1adabbaa0
<backtrace_helper>, trace_argument=0x7fa197875f20) at
../../../libgcc/unwind.inc:290
#3 0x00007fa1adabbc16 in __GI___backtrace (array=<optimized out>, size=200) at
../sysdeps/x86_64/backtrace.c:109
#4 0x00007fa1af423eda in _gf_msg_backtrace_nomem (level=GF_LOG_ALERT,
stacksize=200) at logging.c:1115
#5 0x00007fa1af431717 in gf_print_trace (signum=11, ctx=0x159a010) at
common-utils.c:954
#6 0x000000000040e09c in glusterfsd_print_trace (signum=11) at
glusterfsd.c:2316
#7 <signal handler called>
#8 0x00007fa1a084b0d3 in ?? ()
#9 0x00007fa1ae1dce25 in start_thread (arg=0x7fa197877700) at
pthread_create.c:308
#10 0x00007fa1adaa5bad in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113
(gdb) disassemble
Dump of assembler code for function uw_frame_state_for:
...
0x00007fa1a26a60ac <+1068>: mov 0x90(%r13),%rdx
0x00007fa1a26a60b3 <+1075>: mov $0x5,%eax
=> 0x00007fa1a26a60b8 <+1080>: cmpb $0x48,(%rcx)
0x00007fa1a26a60bb <+1083>: jne 0x7fa1a26a5e8d
<uw_frame_state_for+525>
...
(gdb) info registers
rax 0x5 5
rbx 0x7fa197875c70 140332008692848
rcx 0x7fa1a084b0d3 140332159512787
...
(gdb) x/x $rcx
0x7fa1a084b0d3: Cannot access memory at address 0x7fa1a084b0d3
(gdb) t 1
[Switching to thread 1 (Thread 0x7fa197877700 (LWP 25856))]
#0 x86_64_fallback_frame_state (context=0x7fa197875c70,
context=0x7fa197875c70, fs=0x7fa197875d60) at ./md-unwind-support.h:58
58 if (*(unsigned char *)(pc+0) == 0x48
(gdb) info locals
pc = 0x7fa1a084b0d3 <Address 0x7fa1a084b0d3 out of bounds>
sc = <optimized out>
new_cfa = <optimized out>
Test: https://build.gluster.org/job/regression-test-burn-in/4127/consoleText
Core was generated by `/build/install/sbin/glusterfsd -s 127.1.1.1 --volfile-id
patchy.127.1.1.1.d-bac'.
Program terminated with signal 11, Segmentation fault.
#0 x86_64_fallback_frame_state (context=0x7f26e9ea9c70,
context=0x7f26e9ea9c70, fs=0x7f26e9ea9d60) at ./md-unwind-support.h:58
58 if (*(unsigned char *)(pc+0) == 0x48
(gdb) bt
#0 x86_64_fallback_frame_state (context=0x7f26e9ea9c70,
context=0x7f26e9ea9c70, fs=0x7f26e9ea9d60) at ./md-unwind-support.h:58
#1 uw_frame_state_for (context=context at entry=0x7f26e9ea9c70,
fs=fs at entry=0x7f26e9ea9d60) at ../../../libgcc/unwind-dw2.c:1253
#2 0x00007f26f6250fb9 in _Unwind_Backtrace (trace=0x7f270164faa0
<backtrace_helper>, trace_argument=0x7f26e9ea9f20) at
../../../libgcc/unwind.inc:290
#3 0x00007f270164fc16 in __GI___backtrace (array=<optimized out>, size=200) at
../sysdeps/x86_64/backtrace.c:109
#4 0x00007f2702f2429b in _gf_msg_backtrace_nomem (level=GF_LOG_ALERT,
stacksize=200) at
/home/jenkins/root/workspace/regression-test-burn-in/libglusterfs/src/logging.c:1115
#5 0x00007f2702f2d1dd in gf_print_trace (signum=11, ctx=0x125a010) at
/home/jenkins/root/workspace/regression-test-burn-in/libglusterfs/src/common-utils.c:954
#6 0x000000000040a84a in glusterfsd_print_trace (signum=11) at
/home/jenkins/root/workspace/regression-test-burn-in/glusterfsd/src/glusterfsd.c:2316
#7 <signal handler called>
#8 0x00007f26f4497a07 in ?? ()
#9 0x00007f2701d70e25 in start_thread (arg=0x7f26e9eab700) at
pthread_create.c:308
#10 0x00007f2701639bad in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113
(gdb) info locals
pc = 0x7f26f4497a07 <Address 0x7f26f4497a07 out of bounds>
sc = <optimized out>
new_cfa = <optimized out>
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list