Extending RSP with vCont;n and vCont;f

[Pedro Alves]

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