From: John Gilmore <gnu@toad.com>
To: gdb@sourceware.org
Subject: Re: PR13901
Date: Tue, 03 Apr 2012 07:28:00 -0000 [thread overview]
Message-ID: <201204030728.q337SMWD018124@new.toad.com> (raw)
In-Reply-To: <4F79AFF4.9000704@redhat.com>
> If we can't skip darwin_set_sstep for all continues that are not single-steps,
> we could at least skip those while starting up (when continuing the shell
> until we see enough execs). That'd suggest a new flag like
> darwin-nat.h:struct private_inferior->starting_up, set and cleared in
> darwin_create_inferior, and then making darwin_resume_thread do ...
When I was maintaining GDB (many years ago), touching *anything* in
the state machine that figured out what to do next when the inferior
stopped was guaranteed to produce several bugs for every fix.
In the changes we made, I tried to reduce that tendency, and make
the code more modular and less fragile. Today, "just" adding a new
flag for this may be as simple as you hope.
John Gilmore
next prev parent reply other threads:[~2012-04-03 7:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 13:42 PR13901 Jack Howarth
2012-03-30 14:19 ` PR13901 Tristan Gingold
2012-04-02 10:44 ` PR13901 Tristan Gingold
2012-04-02 11:57 ` PR13901 Tristan Gingold
2012-04-02 13:17 ` PR13901 Jack Howarth
2012-04-02 13:22 ` PR13901 Tristan Gingold
2012-04-02 13:56 ` PR13901 Pedro Alves
2012-04-02 14:07 ` PR13901 Tristan Gingold
2012-04-02 14:17 ` PR13901 Pedro Alves
2012-04-02 14:25 ` PR13901 Tristan Gingold
2012-04-02 14:59 ` PR13901 Andreas Schwab
2012-04-02 15:08 ` PR13901 Tristan Gingold
2012-04-02 15:23 ` PR13901 Pedro Alves
2012-04-02 16:22 ` PR13901 Andreas Schwab
2012-04-02 16:31 ` PR13901 Pedro Alves
2012-04-02 17:28 ` PR13901 Andreas Schwab
2012-04-03 7:28 ` John Gilmore [this message]
2012-04-04 14:23 ` PR13901 Pedro Alves
2012-04-04 14:47 ` PR13901 Tristan Gingold
2012-04-04 15:01 ` PR13901 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=201204030728.q337SMWD018124@new.toad.com \
--to=gnu@toad.com \
--cc=gdb@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).