This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: WG: 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: Fri, 25 Oct 2013 16:36:08 +0100
- Subject: Re: WG: 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> <7E3A266F5548C442BC08FA3038B5197C68449C77 at ATFKEX06 dot bachmann dot at> <52678559 dot 6040004 at codesourcery dot com>
On 10/23/2013 09:14 AM, Yao Qi wrote:
> Sorry for the delayed reply.
>
> On 10/09/2013 07:37 PM, ILG.Robert wrote:
>> "Next" does not skip a whole line. It only skips a possible function call. Such no DWARF2 information is needed - only the stack and the a few assembler instructions need to be evaluated.
But really that is solving the problem at the wrong place. If the
user does "si" himself and that gets into one of those assembly
functions, and then the user does "backtrace", he should see the
real caller of the assembly function. If that doesn't work, then
the unwind info of the assembly functions should be fixed. vCont;n
is just solving one symptom of a more fundamental problem, not the
root issue.
> Generally, hardware breakpoints can be used for read-only regions. If
> your hardware has hw breakpoints, GDB or your stub can switch breakpoint
> to hw breakpoint if the region is read-only or the address is within
> your system code. Looks it is easier to do it inside your stub. People
> who familiar with breakpoint can give comments too.
Agreed. Robert, for the GDB side, see "set breakpoint auto-hw on" at:
https://sourceware.org/gdb/onlinedocs/gdb/Set-Breaks.html
--
Pedro Alves