Re: stacktrace gan on raspberry pi

[Joakim Strandberg <joakimds@kth.se>]

måndag 10 maj 2021 kl. 18:01:53 UTC+2 skrev björn lundin:
> Hi! 
> I got a raspberry pi 4 - 8 Gb, with 
> Ubuntu 20.04 LTS on. 
> 
> I use the gnat provided by apt - 
> 
> 
> ubuntu@ubuntu:~/svn/wcs-std/target/message$ gnatls -v 
> 
> GNATLS 9.3.0 
> Copyright (C) 1997-2019, Free Software Foundation, Inc. 
> 
> Source Search Path: 
> <Current_Directory> 
> /usr/lib/gcc/aarch64-linux-gnu/9/adainclude 
> 
> 
> Object Search Path: 
> <Current_Directory> 
> /usr/lib/gcc/aarch64-linux-gnu/9/adalib 
> 
> 
> Project Search Path: 
> <Current_Directory> 
> /home/ubuntu/svn/wcs-std/config/gpr 
> /home/ubuntu/svn/wcs-std/config/gpr/unix 
> /usr/aarch64-linux-gnu/lib/gnat 
> /usr/aarch64-linux-gnu/share/gpr 
> /usr/share/gpr 
> /usr/lib/gnat 
> 
> 
> I seem to get some info out on a crash 
> 
> Exception raised : GNU.DB.SQLCLI.INVALID_FUNCTION_SEQUENCE 
> 
> Message : [Proc=SQLFetch][Server=][State=HY010][unixODBC][Driver 
> Manager]Function sequence error 
> raised GNU.DB.SQLCLI.INVALID_FUNCTION_SEQUENCE : 
> [Proc=SQLFetch][Server=][State=HY010][unixODBC][Driver Manager]Function 
> sequence error 
> Call stack traceback locations: 
> 0xaaaab8fc2b84 0xaaaab8fc5924 0xaaaab900c364 0xaaaab90024dc 
> 0xaaaab8fbab48 0xaaaab8fbe364 0xaaaab8fb9848 0xffffa687c08c 0xaaaab8fb9898 
> 
> 
> but addr2line gives 
> 
> ubuntu@ubuntu:~/svn/wcs-std/target/message$ addr2line -e 
> ./message_utility 0xaaaab8fc2b84 0xaaaab8fc5924 0xaaaab900c364 
> 0xaaaab90024dc 0xaaaab8fbab48 0xaaaab8fbe364 0xaaaab8fb9848 
> 0xffffa687c08c 0xaaaab8fb9898 
> ??:0 
> ??:0 
> ??:0 
> ??:0 
> ??:0 
> ??:0 
> ??:0 
> ??:0 
> ??:0 
> 
> 
> Is stacktracing not implemented (which i suspect it is not) or is there 
> another tool to use? (like atos on macos) 
> 
> 
> -- 
> Björn

Hi Björn,

According to what I've heard but not checked it myself, the Ada-runtime for the GNAT FSF compiler is not compiled with symbol information and it is therefore not possible to get stacktrace from exceptions that originate from inside the standard library. However, you should be able to see the stack-trace from your own code.

Best regards,
Joakim