Re: GDB call and p func() on embedded target

[Simon Marchi <simon.marchi@polymtl.ca>]

On 2021-08-14 6:28 a.m., Maximilian Schneider via Gdb wrote:
> Hello,
> 
> I am trying to call a function from withing a gdb debugging session on
> an embedded target. However gdb never returns and when i stop it
> manually the program counter is in a strange place. It appears that gdb
> is not able to catch the return, and is continuing  execution from
> before the core was halted... 
> 
> assume the function I want to call has prototype int32_t Init(void);
> 
> If I set the pc manually I can step throught the function until the
> return without a problem.
> 
> I can even set a breakpoint on Init and then use p Init(). The
> breakpoint will fire and I can step throught the code manually.
> 
> eg.
> 
> target remote localhost:3333
> monitor reset halt
> monitor reset init
> file loader.elf
> load loader.elf
> set $sp=0x20010000
> set $pc=&Init
> b Init
> p Init()
> n
> n
> n
> ...
> 
> However without the breakpoint gdb never returns.
> Is this a known problem? Is there a workaround?
> 
> Some background:
> The purpose of this entire excercise is to arrive at a tool/set of
> scripts that can be used to load and execute arbitrary code from RAM,
> to fi. manipulate external memories or run tests.
> 
> Regards,
> M

Hi Maximilian,

I don't think there would be a way to solve this other than debugging
GDB itself, stepping in the call_function_by_hand_dummy function to
understand what it does, how it sets up the dummy stack frame, what
technique it uses to put the breakpoint that should lead to the function
call being completed, etc..  And also running with "set debug infrun 1"
and possibly stepping through handle_inferior_event, to see why GDB
doesn't realize the function call isn't over.

The call_function_by_hand_dummy really lacks debug prints, making it
hard to debug when it goes wrong.  I was debugging another function call
issue the other day, and thought to myself that it would be a good time
to add some.

Also, inferior function call has a lot of arch-specific components to
it, so if you could mention the arch you are working on, it could help
narrow things down.

Simon