Generating exception or doing a call to dump_stack inside a library creates a stack trace which sometimes is wrong.
Original Reporter info from Mantis: Cyrax
-
Reporter name:
Original Reporter info from Mantis: Cyrax
- Reporter name:
Description:
Sometimes the stack trace output is missing the stack info completely or have it partially.
See attached animated picture for more insight about this bug.
Additional information:
FPC trunk 3.3.1 r47063 i386-linux was built with these options :
make clean all install OS_TARGET=linux CPU_TARGET=i386 OPT="-gw2 -godwarfsets -godwarfmethodclassprefix -gl -O- -Xs- -Si- -vbq -Sew- -XX- -CX- -dEXTDEBUG -vh- -vn- -vw- -dDEBUG_NODE_XML -Cit -gt -gv -Cg -Fl/lib -Fl/usr/lib -Fl/usr/lib/gcc/i686-pc-linux-gnu/10.2.0 -dTEST_WIN32_SEH" FPC=fpc REVSTR=47063 IDE=1 NOWPOCYCLE=1 ALLOW_WARNINGS=1 LINKSMART=0 CREATESMART=0 INSTALL_PREFIX="/mnt/shares/ohjelmointi2/fpc/i386/trunk/3.3.1/binary/trunk"
Mantis conversion info:
- Mantis ID: 37892
- OS: Arch
- OS Build: 3.17.4-1
- Build: r47063
- Platform: Linux x86_64
- Version: 3.3.1