Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH 11/12] Use reinsert_breakpoint for vCont;s
Date: Tue, 14 Jun 2016 13:14:00 -0000	[thread overview]
Message-ID: <86h9cvud2z.fsf@gmail.com> (raw)
In-Reply-To: <61835b69-a4bf-a912-4eb3-b223c2a16614@redhat.com> (Pedro Alves's	message of "Mon, 13 Jun 2016 16:55:29 +0100")

Pedro Alves <palves@redhat.com> writes:

>> @@ -4293,7 +4313,7 @@ linux_resume_one_lwp_throw (struct lwp_info *lwp,
>>  
>>        step = maybe_hw_step (thread);
>>      }
>> -  else
>> +  else if (lwp->resume != NULL && lwp->resume->kind != resume_step)
>>      {
>>        /* If the thread isn't doing step-over, there shouldn't be any
>>  	 reinsert breakpoints.  */
>
> Consider (non-stop RSP):
>
>  -> vCont;s:1
>  <- OK
>  -> vCont;s:2
>  <- OK
>
> The handling of the second vCont sets thread 1's lwp->resume to NULL.

If so, the assert won't be called for thread 1.

> The lwp->resume pointer is only meaningful within linux_resume
> and its callees.  (But this function is called in other contexts.)
>

When I wrote the patch, it took me a while to think about this condition
check.  I wanted to remove this condition and assert, but finally
decided to leave it there, as it is not harmful.  If lwp->resume is only
meaningful within linux_resume and its callees, how about remove the
condition check and assert here?

>> @@ -5009,12 +5033,52 @@ linux_resume (struct thread_resume *resume_info, size_t n)
>>  	debug_printf ("Resuming, no pending status or step over needed\n");
>>      }
>>  
>> +  /* Before we resume the threads, if resume_step is requested by GDB,
>> +     stop all threads and install reinsert breakpoints.  */
>
> Looking again, I think the rationale for stopping threads should
> be mentioned here, as it's not obvious.
>

How about this,

  /* Before we resume the threads, if resume_step is requested by GDB,
     we need to access the inferior memory to install reinsert
     breakpoints, so stop all threads.  */

>> @@ -5110,7 +5174,8 @@ proceed_one_lwp (struct inferior_list_entry *entry, void *except)
>>        if (debug_threads)
>>  	debug_printf ("   stepping LWP %ld, client wants it stepping\n",
>>  		      lwpid_of (thread));
>> -      step = 1;
>> +
>> +      step = maybe_hw_step (thread);
>>      }
>>    else if (lwp->bp_reinsert != 0)
>>      {
>> @@ -5176,6 +5241,30 @@ proceed_all_lwps (void)
>>    if (debug_threads)
>>      debug_printf ("Proceeding, no step-over needed\n");
>>  
>> +  /* Re-install the reinsert breakpoints on software single step target
>> +     if the client wants it step.  */
>> +  if (can_software_single_step ())
>
> Not immediately obvious to why is this necessary.  Where were they
> removed in the first place?  I'm it must be necessary, but maybe
> extending the comment helps.

How about this

  /* On software single step target, we removed reinsert breakpoints
     after we get any events from the inferior.  If the client wants
     thread step, re-install these reinsert breakpoints.  */

-- 
Yao (齐尧)


  reply	other threads:[~2016-06-14 13:14 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02  9:31 [PATCH 00/12 V2] Use reinsert breakpoint " Yao Qi
2016-06-02  9:31 ` [PATCH 10/12] Switch current_thread to lwp's thread in install_software_single_step_breakpoints Yao Qi
2016-06-13 15:26   ` Pedro Alves
2016-06-02  9:31 ` [PATCH 05/12] Handle reinsert breakpoints for vforked child Yao Qi
2016-06-13 15:07   ` Pedro Alves
2016-06-02  9:31 ` [PATCH 11/12] Use reinsert_breakpoint for vCont;s Yao Qi
2016-06-13 15:55   ` Pedro Alves
2016-06-14 13:14     ` Yao Qi [this message]
2016-06-14 15:48       ` Pedro Alves
2016-06-15 16:41         ` Yao Qi
2016-06-17 15:10           ` Pedro Alves
2016-06-20 18:09             ` Antoine Tremblay
2016-06-02  9:31 ` [PATCH 02/12] More assert checks on reinsert breakpoint Yao Qi
2016-06-13 14:25   ` Pedro Alves
2016-06-02  9:31 ` [PATCH 04/12] Delete reinsert breakpoints from forked child Yao Qi
2016-06-13 15:02   ` Pedro Alves
2016-06-13 16:53     ` Yao Qi
2016-06-13 17:29       ` Pedro Alves
2016-06-14 11:17         ` Yao Qi
2016-06-14 11:40           ` Pedro Alves
2016-06-17  9:53             ` Yao Qi
2016-06-02  9:31 ` [PATCH 12/12] Support vCont s and S actions with software single step Yao Qi
2016-06-13 15:56   ` Pedro Alves
2016-06-02  9:31 ` [PATCH 07/12] Create sub classes of 'struct breakpoint' Yao Qi
2016-06-13 15:09   ` Pedro Alves
2016-06-02  9:31 ` [PATCH 08/12] Refactor clone_all_breakpoints Yao Qi
2016-06-13 15:14   ` Pedro Alves
2016-06-02  9:31 ` [PATCH 09/12] Make reinsert_breakpoint thread specific Yao Qi
     [not found]   ` <71a5322e-41e3-9e23-df73-e14b14c1d656@redhat.com>
2016-06-14 12:52     ` Yao Qi
2016-06-14 12:57       ` Pedro Alves
2016-06-02  9:31 ` [PATCH 01/12] Switch to current thread in finish_step_over Yao Qi
2016-06-13 14:25   ` Pedro Alves
2016-06-02  9:31 ` [PATCH 06/12] Pass breakpoint type in set_breakpoint_at Yao Qi
2016-06-13 15:07   ` Pedro Alves
2016-06-02  9:31 ` [PATCH 03/12] Step over exit with reinsert breakpoints Yao Qi
2016-06-13 14:37   ` Pedro Alves
2016-06-13 14:52     ` Yao Qi
2016-06-13 15:01       ` Pedro Alves
2016-06-17  9:50         ` 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=86h9cvud2z.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