Home/ Questions/Q 3602066
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T20:41:59+00:00

I get this weird backtrace (sometimes): (gdb) bt #0 0x00002b36465a5d4c in AY16_Loop_M16 () from

  • 0

I get this weird backtrace (sometimes):

(gdb) bt
#0  0x00002b36465a5d4c in AY16_Loop_M16 () from /opt/intel/mkl/10.0.3.020/lib/em64t/libmkl_mc.so
#1  0x00000000000021da in ?? ()
#2  0x00000000000021da in ?? ()
#3  0xbf3e9dec2f04aeff in ?? ()
#4  0xbf480541bd29306a in ?? ()
#5  0xbf3e6017955273e8 in ?? ()
#6  0xbf442b937c2c1f37 in ?? ()
#7  0x3f5580165832d744 in ?? ()
...

Any ideas why i cant see the symbols? Compiled with debugging syms of course.
The same session gives symbols at other points.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The AY16_Loop_M16() in libmkl_mc.so most likely was written in assembly, and does not have correct unwind descriptors, which are required for GDB to properly unwind stack on x86_64 (in the absence of frame pointers).

    Your best bet is to contact Intel, and ask them to add proper unwind descriptors.

    You may get better results if you set a breakpoint on the start of AY16_Loop_M16 — if it is called from C (or any other non-assembly language), chances are you’ll get a reasonable stack trace on entry.

    • 0