Why application crashes when backtrace() called from within signal handler?

Solution In Progress - Updated -

Issue

  • Why does application crash when backtrace() called from within signal handler?
(gdb) where
#0  0x000000376f40f807 in ?? () from /lib64/libgcc_s.so.1
#1  0x000000376f4100b9 in _Unwind_Backtrace () from /lib64/libgcc_s.so.1
#2  0x00000037640fca9e in backtrace () from /lib64/libc.so.6
#3  0x00000000009ea77d in uttraceback ()
#4  0x00000000009ed4f7 in uttrace ()
#5  0x00000000009ed38d in utcore ()
#6  0x0000000000458f6f in drexit ()
#7  0x00000000004beff4 in drSigFatal ()
#8  <signal handler called>
#9  0x000000376f40f807 in ?? () from /lib64/libgcc_s.so.1
#10 0x000000376f4100b9 in _Unwind_Backtrace () from /lib64/libgcc_s.so.1
#11 0x00000037640fca9e in backtrace () from /lib64/libc.so.6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content