From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Ilya Basin <basinilya@gmail.com>, gdb@sourceware.org
Subject: Re: feature request: set step-mode smart
Date: Wed, 25 Apr 2012 09:44:00 -0000 [thread overview]
Message-ID: <20120425114420.Horde.vTwDIEisJlFPl8d0GiwUFMA@mail.elis.ugent.be> (raw)
In-Reply-To: <m37gx4qz07.fsf@redhat.com>
Sergio Durigan Junior wrote on Wed, 25 Apr 2012:
> On Saturday, April 21 2012, Ilya Basin wrote:
>
>> I think, gdb should try to stepi a fixed number of instructions (~100)
>> searching for a code line and if not found, step out.
>
> Thanks for the message. Could you please also create an entry in the
> GDB Bugzilla as well? The link is http://sourceware.org/bugzilla/
>
> This is not a guarantee that someone will actually implement this
> request, but at least we can keep a record of such things.
I'd definitely immediately add a "me too". Our compiler also generates
dispatch stubs without debug info in a number of cases, and adding
code to gdb to recognize all possible variations on all architectures
we support (about 8 by now, I think) is not something anyone has felt
up to figuring out yet. In the long term, it also does not seem
tenable to add pattern recognition to gdb for stubs generated by all
possible compilers (and possibly different versions of those compilers).
Jonas
next prev parent reply other threads:[~2012-04-25 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 11:07 Ilya Basin
2012-04-25 3:20 ` Sergio Durigan Junior
2012-04-25 9:44 ` Jonas Maebe [this message]
2012-04-25 10:08 ` Re[2]: " Ilya Basin
2012-04-25 10:40 ` Jonas Maebe
2012-04-25 10:55 ` Kevin Pouget
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=20120425114420.Horde.vTwDIEisJlFPl8d0GiwUFMA@mail.elis.ugent.be \
--to=jonas.maebe@elis.ugent.be \
--cc=basinilya@gmail.com \
--cc=gdb@sourceware.org \
--cc=sergiodj@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).