Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: pedro@codesourcery.com (Pedro Alves)
Cc: gdb-patches@sourceware.org, drow@false.org
Subject: [rfc] [0/7] infrun cleanup
Date: Sun, 07 Dec 2008 00:16:00 -0000	[thread overview]
Message-ID: <200812070015.mB70FKfE017783@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <200811172102.56650.pedro@codesourcery.com> from "Pedro Alves" at Nov 17, 2008 09:02:56 PM

Pedro Alves wote:
> On Monday 17 November 2008 20:30:05, Ulrich Weigand wrote:
> > In fact other members of the ecs struct should probably be
> > local variables, maybe some of them passed explicitly to
> > subroutines.  I think this would help simplify understanding
> > the data-flow along handle_inferior_event and its subroutines ...
> 
> Agreed, probably, maybe.  I few months ago I started doing something like
> that and got rid of ecs completely, but then I looked at the result and
> noticed that cutting handle_inferior_event into smaller pieces first
> (or at the same time) would probably have had better immediate clarity
> gains, but I didn't try it.  That colides a bit (and possibly goes in the
> opposite direction) with just plain getting rid of ecs, as by doing the
> latter, you find yourself adjusting callers of callers to pass new flags
> around (as opposed to having everything related to an event handy in a
> single struct).  That's a > similar argument to the recent struct
> value_print_options or replacing > current_language with passing a
> struct around or similars.
> 
> Anyway, I don't have that much strong feelings in either direction, just
> telling the world my (possibly bogus) war story.  Patches do speak
> much louder than words.  :-)

OK, here's a couple of patches :-)  These will completely eliminate
struct execution_control_state, while at the same time making the
overall flow of control though handle_inferior_event clearer, IMO.

I'd appreciate any feedback on this approach (in particular if 
you've done things differently in your attempt) ...

Overall patch set tested on amd64-linux with no regressions.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2008-12-07  0:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-15 16:42 [rfc] Fix PR 2250 - multithreaded single-step problems in all-stop mode Ulrich Weigand
2008-11-15 21:30 ` Pedro Alves
2008-11-17 22:19   ` Ulrich Weigand
2008-11-17 23:36     ` Pedro Alves
2008-11-18  1:43       ` Ulrich Weigand
2008-11-18  3:36         ` Pedro Alves
2008-12-07  0:16           ` Ulrich Weigand [this message]
2008-12-07  1:29             ` [rfc] [0/7] infrun cleanup Pedro Alves
2008-12-07 17:12               ` Pedro Alves
2008-12-07 18:20                 ` Ulrich Weigand
2008-12-07 19:16                   ` Pedro Alves

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=200812070015.mB70FKfE017783@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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