Libgnat registers signal handlers which prevents a proper core dump

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.10.0
DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
2.1.0
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

Issue Description
my app links against nvidia libs that use libgnat (namely libnvscisync.so).
it seems that libgnat registers handlers for signals like SIGABRT and SIGSEGV.
when my application encounters a segmentation fault, i want to get a core dump i could debug. instead, i get a printout originating from libgnat - raised STORAGE_ERROR : stack overflow or erroneous memory access.
if i explicitly unregister the signal handlers in my app, i’m able to get a normal core dump, but then i’m not sure what libgnat functionality i may be breaking.
what is the recommended way to work around this?

Error String
raised STORAGE_ERROR : stack overflow or erroneous memory access

Dear @TS_AB ,
Could you please share steps/sample to reproduce the issue?