SIGSEGV in '_Unwind_Backtrace'

Soumya Koduri skoduri@redhat.com
Mon Dec 21 18:03:00 GMT 2015



On 12/21/2015 06:28 PM, Jonathan Wakely wrote:
> On 21 December 2015 at 12:46, Markus Trippelsdorf wrote:
>> On 2015.12.21 at 18:09 +0530, Soumya Koduri wrote:
>>> Hi,
>>>
>>> We are running into "Segmentation fault" in libgcc with below back trace
>>> (not often though) at times. Appreciate any help in debugging and resolving
>>> it.
>>>
>>> Program terminated with signal 11, Segmentation fault.
>>> #0  0x00007f800426f867 in ?? () from ./lib64/libgcc_s.so.1
>>> Missing separate debuginfos, use: debuginfo-install
>>> glibc-2.12-1.132.el6_5.1.x86_64 keyutils-libs-1.4-4.el6.x86_64
>>> krb5-libs-1.10.3-10.el6_4.6.x86_64 libcom_err-1.41.12-18.el6.x86_64
>>> libgcc-4.4.7-4.el6.x86_64 libselinux-2.0.94-5.3.el6_4.1.x86_64
>>> openssl-1.0.1e-15.el6.x86_64 zlib-1.2.3-29.el6.x86_64
>>> (gdb) bt
>>> #0  0x00007f800426f867 in ?? () from ./lib64/libgcc_s.so.1
>>> #1  0x00007f8004270119 in _Unwind_Backtrace () from ./lib64/libgcc_s.so.1
>>> #2  0x00007f800fb46936 in backtrace () from ./lib64/libc.so.6
>>> #3  0x00007f8010ee6f73 in _gf_msg_backtrace_nomem (level=GF_LOG_ALERT,
>>> stacksize=200)
>>>      at /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/libglusterfs/src/logging.c:1090
>>> #4  0x00007f8010eecd38 in gf_print_trace (signum=11, ctx=0xda7010)
>>>      at /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/libglusterfs/src/common-utils.c:740
>>> #5  0x00000000004098d6 in glusterfsd_print_trace (signum=11)
>>>      at /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/glusterfsd/src/glusterfsd.c:2033
>>> #6  <signal handler called>
>>> #7  0x00007f7fff1aa561 in ?? ()
>>> #8  0x00007f80101c6a51 in start_thread () from ./lib64/libpthread.so.0
>>> #9  0x00007f800fb3093d in clone () from ./lib64/libc.so.6
>>> (gdb)
>>
>> 4.4.7 is ancient and not supported anymore. Please try a more recent
>> version.
>
> Or report it to Red Hat's bugzilla. It's supported in RHEL, but not upstream.
>
Sure. Thanks!

- Soumya



More information about the Gcc-help mailing list