From: Pedro Alves <pedro@codesourcery.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org, drow@false.org
Subject: Re: [rfc] Fix PR 2250 - multithreaded single-step problems in all-stop mode
Date: Tue, 18 Nov 2008 03:36:00 -0000 [thread overview]
Message-ID: <200811172102.56650.pedro@codesourcery.com> (raw)
In-Reply-To: <200811172030.mAHKU54d002481@d12av02.megacenter.de.ibm.com>
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. :-)
--
Pedro Alves
next prev parent reply other threads:[~2008-11-17 21:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 16:42 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 [this message]
2008-12-07 0:16 ` [rfc] [0/7] infrun cleanup Ulrich Weigand
2008-12-07 1:29 ` 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=200811172102.56650.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=drow@false.org \
--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