From: Pedro Alves <pedro@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org, Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: Get rid of stop_pc (was: [RFA] dummy frame handling cleanup, plus inferior fun call signal handling improvement)
Date: Fri, 05 Dec 2008 02:14:00 -0000 [thread overview]
Message-ID: <200812050213.09380.pedro@codesourcery.com> (raw)
In-Reply-To: <e394668d0812041749u349eb483n43efa85914a5a5b@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
On Friday 05 December 2008 01:49:02, Doug Evans wrote:
> Nit.
>
> The check for !frame isn't related to removing stop_pc. Separate
> patch or add a changelog entry?
Oops, sorry. That is dead code. There is always a frame nowadays.
get_current_frame either returns a frame, or throws --- never
returns NULL.
I've checked in the below.
--
Pedro Alves
[-- Attachment #2: no_frame_core_dump.diff --]
[-- Type: text/x-diff, Size: 665 bytes --]
2008-12-05 Pedro Alves <pedro@codesourcery.com>
* infcmd.c (step_once): Remove dead code.
---
gdb/infcmd.c | 2 --
1 file changed, 2 deletions(-)
Index: src/gdb/infcmd.c
===================================================================
--- src.orig/gdb/infcmd.c 2008-12-05 01:57:41.000000000 +0000
+++ src/gdb/infcmd.c 2008-12-05 02:00:17.000000000 +0000
@@ -928,8 +928,6 @@ step_once (int skip_subroutines, int sin
clear_proceed_status ();
frame = get_current_frame ();
- if (!frame) /* Avoid coredump here. Why tho? */
- error (_("No current frame"));
tp->step_frame_id = get_frame_id (frame);
if (!single_inst)
next prev parent reply other threads:[~2008-12-05 2:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 21:01 [RFA] dummy frame handling cleanup, plus inferior fun call signal handling improvement Doug Evans
2008-11-19 14:07 ` Doug Evans
2008-11-20 15:02 ` Doug Evans
2008-11-20 15:06 ` Doug Evans
2008-12-01 20:52 ` Doug Evans
2008-12-01 21:22 ` Pedro Alves
2008-12-02 1:20 ` Doug Evans
2008-12-03 6:04 ` Doug Evans
2008-12-04 15:32 ` Ulrich Weigand
2008-12-04 15:54 ` Pedro Alves
2008-12-04 22:32 ` Doug Evans
2008-12-04 22:42 ` Pedro Alves
2008-12-05 0:18 ` Ulrich Weigand
2008-12-05 0:37 ` Pedro Alves
2008-12-05 1:16 ` Get rid of stop_pc (was: [RFA] dummy frame handling cleanup, plus inferior fun call signal handling improvement) Pedro Alves
2008-12-05 1:50 ` Doug Evans
2008-12-05 2:14 ` Pedro Alves [this message]
2008-12-05 2:46 ` Pedro Alves
2008-12-05 18:43 ` Ulrich Weigand
2008-12-05 19:07 ` Pedro Alves
2008-12-05 0:30 ` [RFA] dummy frame handling cleanup, plus inferior fun call signal handling improvement Ulrich Weigand
2008-11-26 19:17 ` Doug Evans
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=200812050213.09380.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dje@google.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