This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Extending RSP with vCont;n and vCont;f
- From: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: "ILG.Robert" <R dot ILG at bachmann dot info>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Mon, 07 Oct 2013 13:05:43 +0100
- Subject: Re: Extending RSP with vCont;n and vCont;f
- Authentication-results: sourceware.org; auth=none
- References: <7E3A266F5548C442BC08FA3038B5197C684495C0 at ATFKEX06 dot bachmann dot at> <525117AF dot 60703 at codesourcery dot com>
On 10/06/2013 08:56 AM, Yao Qi wrote:
> On 10/04/2013 08:53 PM, ILG.Robert wrote:
>> Second our system contains some assembler functions which do not build a stack frame as usually done by compiled c-code. When debugging these assembler functions GDB reacts as usual: it detects the call of external code and does a "continue" to the return address of the current stack frame. Yet this return address is not the caller - it is the caller of the caller and therefore a "step-into" does not only skip undebugable code, it also steps out of the currently debugged function.
>>
>
> IMO, it is not a problem specific to your target. It needs a fix in GDB
> rather than proposing a new rsp packet.
Or really, those assembly functions have wrong or missing unwind info.
--
Pedro Alves