From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 8/8] Fix removing inferiors from within "thread apply" commands
Date: Thu, 13 Apr 2017 11:33:00 -0000 [thread overview]
Message-ID: <86o9w08ru5.fsf@gmail.com> (raw)
In-Reply-To: <1491954673-29172-9-git-send-email-palves@redhat.com> (Pedro Alves's message of "Wed, 12 Apr 2017 00:51:13 +0100")
Pedro Alves <palves@redhat.com> writes:
> @@ -313,9 +319,31 @@ public:
> explicit inferior (int pid);
> ~inferior ();
>
> + /* Returns true if we can delete this inferior. We can't delete it
> + if it is the current inferior, or if there's code out there that
> + relies on it existing (m_refcount > 0). */
> + bool deletable () const
> + {
> + return m_refcount == 0 && this != current_inferior ();
> + }
> +
> /* Pointer to next inferior in singly-linked list of inferiors. */
> struct inferior *next = NULL;
>
> + /* Increase the refcount. */
> + void incref ()
> + {
> + gdb_assert (m_refcount >= 0);
> + m_refcount++;
> + }
> +
> + /* Decrease the refcount. */
> + void decref ()
> + {
> + m_refcount--;
> + gdb_assert (m_refcount >= 0);
> + }
> +
> /* Convenient handle (GDB inferior id). Unique across all
> inferiors. */
> int num = 0;
> @@ -431,6 +459,12 @@ public:
>
> /* Per inferior data-pointers required by other GDB modules. */
> REGISTRY_FIELDS;
> +
> +private:
> + /* If this is > 0, then it means there's code out there that relies
> + on this inferior existing. Don't allow deleting it in that
> + case. */
> + int m_refcount = 0;
> };
Can we move them to a super class, so that both thread and inferior can
extend it?
>
> -/* Switch from one thread to another. */
> +/* Switch to no thread selected. */
>
> -void
> -switch_to_thread (ptid_t ptid)
> +static void
> +switch_to_no_thread ()
> {
> - /* Switch the program space as well, if we can infer it from the now
> - current thread. Otherwise, it's up to the caller to select the
> - space it wants. */
> - if (ptid != null_ptid)
> - {
> - struct inferior *inf;
> + if (inferior_ptid == null_ptid)
> + return;
>
> - inf = find_inferior_ptid (ptid);
> - gdb_assert (inf != NULL);
> - set_current_program_space (inf->pspace);
> - set_current_inferior (inf);
> - }
> + inferior_ptid = null_ptid;
> + reinit_frame_cache ();
> + stop_pc = ~(CORE_ADDR) 0;
> +}
>
> - if (ptid == inferior_ptid)
> +/* Switch from one thread to another. */
> +
> +static void
> +switch_to_thread (thread_info *thr)
> +{
> + gdb_assert (thr != NULL);
> +
> + if (inferior_ptid == thr->ptid)
> return;
>
> - inferior_ptid = ptid;
> + /* Switch the current program space and current inferior as
> + well. */
> + set_current_program_space (thr->inf->pspace);
> + set_current_inferior (thr->inf);
> +
> + inferior_ptid = thr->ptid;
Can these code be replaced by switch_to_thread_no_regs?
--
Yao (齐尧)
next prev parent reply other threads:[~2017-04-13 11:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 23:51 [PATCH 0/8] " Pedro Alves
2017-04-11 23:51 ` [PATCH 8/8] " Pedro Alves
2017-04-13 11:33 ` Yao Qi [this message]
2017-04-13 12:22 ` Pedro Alves
2017-04-13 14:49 ` Pedro Alves
2017-04-19 8:23 ` Yao Qi
2017-04-19 12:15 ` Pedro Alves
2017-04-19 12:20 ` Pedro Alves
2017-04-13 15:31 ` Yao Qi
2017-04-11 23:51 ` [PATCH 6/8] Make inferior a class with cdtors, and use new/delete Pedro Alves
2017-04-13 10:24 ` Yao Qi
2017-04-11 23:51 ` [PATCH 1/8] watch_command_1: Fix dangling frame access Pedro Alves
2017-04-13 9:34 ` Yao Qi
2017-04-13 15:26 ` Pedro Alves
2017-04-11 23:51 ` [PATCH 2/8] Fix follow-fork latent bug Pedro Alves
2017-04-13 9:58 ` Yao Qi
2017-04-13 12:09 ` Pedro Alves
2017-04-13 15:33 ` Yao Qi
2017-04-11 23:51 ` [PATCH 7/8] Make inferior::detaching a bool, and introduce scoped_restore::release() Pedro Alves
2017-04-11 23:51 ` [PATCH 3/8] C++fy thread_apply_all_command Pedro Alves
2017-04-13 10:06 ` Yao Qi
2017-04-11 23:56 ` [PATCH 5/8] GC inferior.c:init_inferior_list Pedro Alves
2017-04-13 10:10 ` Yao Qi
2017-04-11 23:56 ` [PATCH 4/8] Improve coverage of the PR threads/13217 regression test Pedro Alves
2017-04-13 10:09 ` Yao Qi
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=86o9w08ru5.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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