From: Joel Brobecker <brobecker@adacore.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Eliminate frame_id_inner comparisons
Date: Wed, 25 Jun 2008 13:32:00 -0000 [thread overview]
Message-ID: <20080625131043.GD3700@adacore.com> (raw)
In-Reply-To: <200806192034.m5JKY5gt004879@d12av02.megacenter.de.ibm.com>
Hi Ulrich,
> ChangeLog:
>
> * frame.h (struct frame_id): Update comments.
> (frame_id_inner): Remove prototype.
> (enum unwind_stop_reason): Remove UNWIND_INNER_ID and
> UNWIND_SAME_ID, add UNWIND_CYCLE.
> * frame.c (struct frame_info): New member "cycle".
> (frame_id_inner): Delete.
> (frame_find_by_id): Remove frame_id_inner check.
> (create_sentinel_frame): Initialize frame->cycle.
> (get_prev_frame_1): Remove frame_id_inner check. Check for
> cycles in the frame chain using Floyd's algorithm.
> Initialize prev_frame->cycle.
> (frame_stop_reason_string): Handle UNWIND_CYCLE instead of
> UNWIND_INNER_ID and UNWIND_SAME_ID.
>
> * dummy-frame.c (dummy_frame_push): Use frame_find_by_id to
> detect stale dummy frames.
> * stack.c (return_command): Directly pop the selected frame.
> * infrun.c (handle_inferior_event): Remove dead code.
> * i386-tdep.c (i386_push_dummy_call): Update comment.
FWIW, I looked at the patch and I don't see any problem with it.
> + /* This frame has the same ID some frame inner to it. That means
the same ID as some frame
--
Joel
next prev parent reply other threads:[~2008-06-25 13:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 4:42 Ulrich Weigand
2008-06-25 13:32 ` Joel Brobecker [this message]
2008-06-25 14:15 ` Daniel Jacobowitz
2008-08-21 19:43 ` [rfc, v2] Fix frame_id_inner comparison false positives Ulrich Weigand
2008-08-21 20:16 ` Daniel Jacobowitz
2008-08-21 21:47 ` [rfc, v3] " Ulrich Weigand
2008-08-22 1:45 ` Ulrich Weigand
2008-08-26 17:46 ` Ulrich Weigand
2008-08-26 22:19 ` Daniel Jacobowitz
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=20080625131043.GD3700@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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