From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: "ILG.Robert" <R.ILG@bachmann.info>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Extending RSP with vCont;n and vCont;f
Date: Mon, 07 Oct 2013 12:05:00 -0000 [thread overview]
Message-ID: <5252A397.5000803@redhat.com> (raw)
In-Reply-To: <525117AF.60703@codesourcery.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
next prev parent reply other threads:[~2013-10-07 12:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 12:53 ILG.Robert
2013-10-06 7:58 ` Yao Qi
2013-10-07 12:05 ` Pedro Alves [this message]
2013-10-09 11:37 ` WG: " ILG.Robert
-- strict thread matches above, loose matches on Subject: below --
2013-11-08 8:18 ILG.Robert
2013-10-23 7:19 ILG.Robert
2013-10-03 5:04 ILG.Robert
2013-10-02 15:08 ILG.Robert
2013-10-02 16:25 ` Eli Zaretskii
2013-10-04 6:49 ` Yao Qi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5252A397.5000803@redhat.com \
--to=palves@redhat.com \
--cc=R.ILG@bachmann.info \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox