From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/patch] handle_inferior_event() extract some code into a separate function
Date: Fri, 02 Jan 2004 16:29:00 -0000 [thread overview]
Message-ID: <3FF59C76.3000902@gnu.org> (raw)
In-Reply-To: <20031219144323.GL826@gnat.com>
> [I think this patch was sort of pre-approved by Andrew, which explains
> why I put "patch" in the subject, but I prefered to make sure and ask
> for approval again. Hence the RFA]
>
> Hello,
>
> This change is related to a discussion started in the following thread:
> http://sources.redhat.com/ml/gdb-patches/2003-12/msg00037.html
>
> In particular, this implements the suggestion made by Andrew in the
> following message:
> http://sources.redhat.com/ml/gdb-patches/2003-12/msg00279.html
>
> This patch implements the first part, which is to extract the code
> inside the we-stepped-into-a-function if block, and move it to its
> own function. It's fairly mechanical.
>
> The next step will be to change the if condition itself to separate
> out the targets where the new frame code is used from the ones where
> the old one is still in use. I will send a patch as soon as this one
> is reviewed.
M'kay.
Andrew
next prev parent reply other threads:[~2004-01-02 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 14:43 Joel Brobecker
2004-01-02 16:29 ` Andrew Cagney [this message]
2004-01-03 11:52 ` Joel Brobecker
2004-01-03 12:51 ` Mark Kettenis
2004-01-03 13:00 ` Joel Brobecker
2004-01-03 15:01 ` [RFA] infrun.c:handle_inferior_event() tiny simplification (was "Re: [RFA/patch] handle_inferior_event() extract some code into a separate function") Joel Brobecker
2004-01-03 15:09 ` Mark Kettenis
2004-01-03 15:18 ` Joel Brobecker
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=3FF59C76.3000902@gnu.org \
--to=cagney@gnu.org \
--cc=brobecker@gnat.com \
--cc=gdb-patches@sources.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