How to get detailed errors: "F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)"?

[senmx]

01-01 16:54:46.122 20883 20883 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-01 16:54:46.122 20883 20883 F DEBUG   : Build fingerprint: 'google/coral/coral:11/RP1A.200720.009/6720564:user/release-keys'
01-01 16:54:46.122 20883 20883 F DEBUG   : Revision: '0'
01-01 16:54:46.122 20883 20883 F DEBUG   : ABI: 'arm'
01-01 16:54:46.122 20883 20883 F DEBUG   : Timestamp: 2021-01-01 16:54:46+0800
01-01 16:54:46.122 20883 20883 F DEBUG   : pid: 20653, tid: 20744, name: qtMainLoopThrea  >>> xxxxxx <<<
01-01 16:54:46.122 20883 20883 F DEBUG   : uid: 10217
01-01 16:54:46.123 20883 20883 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x6f0062
01-01 16:54:46.123 20883 20883 F DEBUG   :     r0  d51001e8  r1  00000001  r2  00000054  r3  bcffd47c
01-01 16:54:46.123 20883 20883 F DEBUG   :     r4  e666f260  r5  d51001e8  r6  b9c33c10  r7  bcffd490
01-01 16:54:46.123 20883 20883 F DEBUG   :     r8  bcffd4b8  r9  e666f260  r10 ba9a8800  r11 e666f260
01-01 16:54:46.123 20883 20883 F DEBUG   :     ip  006f0063  sp  bcffd478  lr  bc282863  pc  006f0062
01-01 16:54:46.123 20883 20883 F DEBUG   : 
01-01 16:54:46.123 20883 20883 F DEBUG   : backtrace:
01-01 16:54:46.123 20883 20883 F DEBUG   :       #00 pc 006f0062  <unknown>
01-01 16:54:46.123 20883 20883 F DEBUG   :       #01 pc 000ea85f  /data/app/xxxxxx-M-vT35IQfEWkC3DWVSInDA==/lib/arm/libQt5Qml_armeabi-v7a.so (BuildId: 0cd979223f6a7b3dff723df3f145a5c8d62fc19a)

********** Crash dump: **********
Build fingerprint: 'google/coral/coral:11/RP1A.200720.009/6720564:user/release-keys'
#00 0x006f0062 <unknown>
#01 0x000ea85f /data/app/xxxxxx-M-vT35IQfEWkC3DWVSInDA==/lib/arm/libQt5Qml_armeabi-v7a.so (BuildId: 0cd979223f6a7b3dff723df3f145a5c8d62fc19a)
Crash dump is completed

[Christian Ehrlicher]

Use a debugger and take a look in the stack trace to see where the error comes from.

[senmx]

This post is deleted!

[senmx]

@Christian-Ehrlicher I updated the content of the question, please look again.Tks.

[JonB]

@senmx
The code you have written seems to have nothing to do with Qt.

Since you are told

Cause: null pointer dereference

why don't you put some more error checking into your code? For example, maybe r = RSA_new(); is returning nullptr, I don't do, how are you sure it does not? Or, put in some qDebug() statements or similar between the lines so you know where you get to.

[senmx]

@JonB Remove this sentence and it can run normally,at least no error

EVP_PKEY_assign_RSA(evpkey, r);

[JonB]

@senmx
And you did check whether r == nullptr?

In any case, you should look at the documentation of the non-Qt library functions you are calling. Maybe your evpkey data is wrong.

[senmx]

@JonB evpkey and r are not null

[SGaist]

Hi,

Do you base your code on an official example ?
If so can you share it ?

[senmx]

@SGaist The magic is that it is normal to using a demo to test this function separately.Even add this sentence

EVP_PKEY_assign_RSA(evpkey, r);

The key is that you cannot get detailed error logs.

[SGaist]

@senmx said in How to get detailed errors: "F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)"?:

@SGaist The magic is that it is normal to using a demo to test this function separately.

What do you mean by that ?

[senmx]

@SGaist It's okay, it shouldn't be caused by that, the key is is there a way to get detailed logs?

[JonB]

@senmx
This code has nothing to do with Qt, right? You have never even bothered to say what this third-party code belongs to, or where you get your code from. And you'd like someone here to tell you how to get detailed logs out of it?

[senmx]

@JonB Yes. I now suspect that there is a memory leak in EVP_PKEY_assign_RSA, causing the following code to be wrong.

[JonB]

@senmx
Well a memory leak would not cause a crash, rather only some wasted memory. So that should not be the cause of the issue you report.

Despite being asked, you still have not said a word about what this library is and more importantly where you get the sample for the code you have written.....

[senmx]

@JonB Tks. It's just a guessing, it's probably a pointer memory problem.How to get a more detailed error stack?

[SGaist]

@senmx said in How to get detailed errors: "F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)"?:

@JonB Tks. It's just a guessing, it's probably a pointer memory problem.How to get a more detailed error stack?

Install the debug symbols of that library and use a debugger.

[senmx]

@SGaist Okay. Where do I get the library debug symbols, do I compile it myself?

[senmx]

@JonB Presumably you are referring to this question.What library you are asking is just a piece of code. There is no library. My main question is how to get detailed error information. I'm already trying to solve it myself.

[JonB]

@senmx said in How to get detailed errors: "F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)"?:

There is no library.

Oh! So all the code you originally showed, and the EVP_PKEY_assign_RSA(evpkey, r); you still have, is not in a library? It's your own code, with your own source code. And there was I, thinking it was all code from OpenSSL, when in fact it is not, and you just happen to have chosen to name all your own classes/functions to match those supplied from OpenSSL....

So you don't need to install any debug symbols like @SGaist said, you can just look at your own source code. Will be much easier.