Hello @zuuuuk,
“PROCESS: 2022 ,TID 2029” is a part of the backtrace.
→ Please provide the whole content of this backtrace.
It is possible to perform a first analysis of a backtrace without using GDB.
→ See [AirPrime with MDM9x+Legato] How to analyze Legato-level crash v002.pdf (174.2 KB)
According to “Reading symbols from /home/win/legato_vsc3/_build_MSD084/wp750x/app/MSD084/staging/read-only/bin/msdComponent…Reading symbols from /home/win/legato_vsc3/.debug/.build-id/4c/05c27462816e3fd5fd836d9d6d224b14d90402.debug…done.”, the crash origin is your Legato App “MSD084” / Legato Component “msdComponent”.
→ You should tune your Legato App *.adef file, so that belowmentioned limits are higher than the maximum core dump size:
maxMemoryBytes: 60000K // memory usage limit
maxFileSystemBytes: 60000K // RAM file system usage limit
maxCoreDumpFileBytes: 60000K // core dump file size limit
maxFileBytes: 60000K // maximum size that processes can make files
Legato build tools are, by default, stripping the staging tree.
Stripping is actually controlled by this Legato App Framework build option :
STRIP_STAGING_TREE, defined inside legato-af/legato.kconfig at 20.04-release · legatoproject/legato-af · GitHub, default value = y
So, when building a Legato App, if “-d /path/to/myAppDebugSymbols” option is passed to mkapp, then debug symbols are:
o removed from binaries,
o copied into a dedicated folder: /path/to/myAppDebugSymbols/
)
→ Did you use mkapp “-d” option?
KR.