public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/14119] F17: failed assertion `!frame_id_inlined_p (frame_id)'
Date: Thu, 16 Aug 2012 17:48:00 -0000 [thread overview]
Message-ID: <bug-14119-4717-K5DMpFgP1U@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14119-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14119
--- Comment #5 from Tom Tromey <tromey at redhat dot com> 2012-08-16 17:47:22 UTC ---
(In reply to comment #4)
> I believe 'finish' should step out of inlined frames one frame at a time.
> The same like 'step' steps in one frame at a time, also without changing PC.
> The same should apply to tailcall frames (just step-in is irrelevant for them).
I wouldn't mind it, but I don't plan to do it myself.
I think perhaps the fix here ought to just ignore tailcall frames
rather than both tail- and inlined- frames.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-08-16 17:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 18:13 [Bug gdb/14119] New: " jim at meyering dot net
2012-08-15 14:55 ` [Bug gdb/14119] " tromey at redhat dot com
2012-08-15 15:15 ` tromey at redhat dot com
2012-08-15 16:00 ` tromey at redhat dot com
2012-08-15 16:02 ` jan.kratochvil at redhat dot com
2012-08-15 17:23 ` tromey at redhat dot com
2012-08-15 19:49 ` jan.kratochvil at redhat dot com
2012-08-16 17:48 ` tromey at redhat dot com [this message]
2012-08-16 19:00 ` tromey at redhat dot com
2012-09-12 18:04 ` jan.kratochvil at redhat dot com
2012-09-17 7:16 ` cvs-commit at gcc dot gnu.org
2012-09-17 7:18 ` cvs-commit at gcc dot gnu.org
2012-09-17 7:22 ` jan.kratochvil at redhat dot com
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=bug-14119-4717-K5DMpFgP1U@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).