From: William Tambe <tambewilliam@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: gdb command "next" wrongly working as command "step"
Date: Sun, 18 Aug 2019 08:32:00 -0000 [thread overview]
Message-ID: <CAF8i9mNoawng3nbCebbY5ihSi5bwOzVg5YyH6NbaGrxcfTNYEQ@mail.gmail.com> (raw)
In-Reply-To: <20190818041556.GA11323@host1.jankratochvil.net>
On Sat, Aug 17, 2019 at 11:16 PM Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
>
> On Sun, 18 Aug 2019 05:36:34 +0200, William Tambe wrote:
> > I having an issue where the gdb command "next" wrongly work as the
> > command "step", in that it will step-into functions instead of
> > stepping-over functions.
> >
> > To support single stepping I have implemnted set_gdbarch_software_single_step().
> >
> > Is there another function that I need to implement to support
> > stepping-over functions ?
>
> "next" needs properly implemented backtrace/unwinding so that can it can do
> "finish" when "next" detects it stepped into a function.
Can I have suggestions of locations within the gdb code where I could
put breakpoints to trace where the issue I am having is occurring ?
Alternatively, what function within the gdb code implement "next" and "finish" ?
>
>
> Jan
next prev parent reply other threads:[~2019-08-18 8:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-18 3:36 William Tambe
2019-08-18 4:16 ` Jan Kratochvil
2019-08-18 8:32 ` William Tambe [this message]
2019-08-18 9:06 ` Jan Kratochvil
2019-08-23 21:33 ` William Tambe
2019-08-23 21:54 ` Pedro Alves
2019-08-24 3:36 ` William Tambe
2019-08-25 19:04 ` William Tambe
2019-08-26 13:18 ` Pedro Alves
2019-09-01 19:06 ` William Tambe
2019-09-05 11:59 ` Andrew Burgess
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=CAF8i9mNoawng3nbCebbY5ihSi5bwOzVg5YyH6NbaGrxcfTNYEQ@mail.gmail.com \
--to=tambewilliam@gmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).