c - Stack frame NULL in backtrace log -



c - Stack frame NULL in backtrace log -

my application receiving segmentation fault. trace log -

program received signal sigsev, segmentation fault. 0x00000000004a5c03 in engine_unlocked_finish () (gdb) bt #0 0x00000000004a5c03 in engine_unlocked_finish () #1 0x00000000004a5d71 in engine_finish () #2 0x000000000046a537 in evp_pkey_free_it () #3 0x000000000046a91b in evp_pkey_free () #4 0x00000000004b231a in pubkey_cb () #5 0x0000000000470c97 in asn1_item_combine_free () #6 0x0000000000750f70 in x509_cinf_seq_tt () #7 0x00000000010f7d90 in ?? () #8 0x00000000010f7cf0 in ?? () #9 0x0000000000000000 in ?? ()

the stackframe @ #9 interesting. it's address 0x0000000000000000. mean stack got corrupted before getting engine_unlocked_finish () ?

the stackframe @ #9 interesting.

not really. what's happening x509_cinf_seq_tt hand-coded assembly, , lacks right unwind descriptors, after in stack trace bogus.

in fact, looking @ source, x509_cinf_seq_tt not function, it's asn1_item_combine_free starts "bad unwind".

c gdb libcurl debug-backtrace

Comments

Popular posts from this blog

formatting - SAS SQL Datepart function returning odd values -

c++ - Apple Mach-O Linker Error(Duplicate Symbols For Architecture armv7) -

php - Yii 2: Unable to find a class into the extension 'yii2-admin' -