Re: AWS issue

[Simon Wright <simon.j.wright@mac.com>]

Sebastien Morand <seb.morand@gmail.com> writes:

> About addr2line, here is what I got:
> $ addr2line -e hello_world 0x28188ac9 0x2818a535 0x2819196a 0x28183cac
> 0x2819bd94 0x2819e324 0x804d184 0x804d022 0x804c987??:0
> ??:0
> ??:0
> ??:0
> ??:0
> ??:0
> /mnt/programs/opt/src/AWS-gpl-2.3.0/demos/hello_world.adb:43
> /mnt/programs/opt/src/AWS-gpl-2.3.0/.build/release/demos/obj/b~hello_world.adb:447
> ??:0
>
> The problem is
> /mnt/programs/opt/src/AWS-gpl-2.3.0/.build/release/demos/obj/b~hello_world.adb
> does not exist :-)

gnatmake would normally leave it there. This is the actual main
program, constructed by gnatbind, which calls your main procedure.

The useful exception point is hello_world.adb:43.

The situation with having only a hex traceback is where our project is
all the time on an embedded system (VxWorks): even if the addr2line
code was available on the target, the symbolic traceback only works
where you have access to the unstripped executable, and we don't have
room for it on flash. So we keep the unstripped executable and run
addr2line (actually a wrapper, powerpc-wrs-vxworks-vxaddr2line) on
that. You do need to be careful with your config management, of
course!