Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: teawater <teawater@gmail.com>
Cc: Pedro Alves <pedro@codesourcery.com>,
	  "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [reverse/record] adjust_pc_after_break in reverse execution mode?
Date: Thu, 23 Oct 2008 23:28:00 -0000	[thread overview]
Message-ID: <4901076C.8040104@vmware.com> (raw)
In-Reply-To: <daef60380810202351h3d16174cl7be16a9767e413ad@mail.gmail.com>

Hui, can you hold off on this change?

What I'm finding is that I can reproduce the bad behavior
that Pedro demonstrated on the 20080930 branch, but ONLY
if I omit Pedro's change in adjust_pc_after_break.  If I
add Pedro's change, I can no longer reproduce any bad
behavior.

I've added Pedro's change to the branch now -- why don't
you temporarily take out all these changes, and then see
if you can make it manifest a problem.


teawater wrote:
> Sorry for understand your mean so later Pedro. I made a new patch that
> Set pc if forward execute and gdbarch_decr_pc_after_break is not 0 in
> replay mode. How do you think about it?
> 
> 
> And I think 20080930 branch is need your "adjust_pc_reverse.diff". Do
> you mind I check it in?
> 
> On Tue, Oct 21, 2008 at 08:21, Pedro Alves <pedro@codesourcery.com> wrote:
>> On Tuesday 21 October 2008 00:36:12, teawater wrote:
>>> I think your mean is check breakpoint in address
>>> read_pc()+gdbarch_decr_pc_after_break (gdbarch) in record_wait, right?
>> Taking x86 as an example, when you're doing normal debugging and you
>> hit a breakpoint (SIGTRAP), the first read_pc GDB does to check where
>> what breakpoint was hit, will read back `breakpoint_PC + 1' --- GDB takes care
>> getting rid of that `+ 1' offset in infrun.c:adjust_pc_after_break.  The
>> idea is for you to do the same as the kernel/hardware would --- still
>> check for breakpoints at read_pc, but increment PC by 1 before reporting the
>> breakpoint to GDB's core.  E.g., see the `pc += gdbarch...' line from
>> the patch I posted previously, something like:
>>
>> record.c:record_wait ()
>> {
>> ...
>> +         /* Check for breakpoint hits in forward execution.  */
>> +         pc = read_pc ();
>> +         if (execution_direction == EXEC_FORWARD
>> +             && regular_breakpoint_inserted_here_p (pc)
>> +             /* && !single-stepping */)
>> +           {
>> +             status->kind = TARGET_WAITKIND_STOPPED;
>> +             status->value.sig = TARGET_SIGNAL_TRAP;
>> +             if (software_breakpoint_inserted_here_p (pc))
>> +               {
>> +                 pc += gdbarch_decr_pc_after_break (gdbarch);
>> +                 write_pc (pc);
>> +               }
>> +
>>
>> --
>> Pedro Alves
>>
>>
>> ------------------------------------------------------------------------
>>
>> --- a/record.c
>> +++ b/record.c
>> @@ -497,6 +497,30 @@ record_wait (ptid_t ptid, struct target_
>>        int continue_flag = 1;
>>        int first_record_end = 1;
>>        struct cleanup *old_cleanups = make_cleanup (record_wait_cleanups, 0);
>> +      CORE_ADDR tmp_pc;
>> +
>> +      /* Check breakpoint when forward execute.  */
>> +      if (execution_direction == EXEC_FORWARD)
>> +	{
>> +	  tmp_pc = regcache_read_pc (regcache);
>> +	  if (breakpoint_inserted_here_p (tmp_pc))
>> +	    {
>> +	      if (record_debug)
>> +		{
>> +		  fprintf_unfiltered (gdb_stdlog,
>> +				      "Process record: break at 0x%s.\n",
>> +				      paddr_nz (tmp_pc));
>> +		}
>> +	      if (gdbarch_decr_pc_after_break (get_regcache_arch (regcache)))
>> +		{
>> +		  regcache_write_pc (regcache,
>> +				     tmp_pc +
>> +				     gdbarch_decr_pc_after_break
>> +				     (get_regcache_arch (regcache)));
>> +		}
>> +	      goto replay_out;
>> +	    }
>> +	}
>>  
>>        record_get_sig = 0;
>>        act.sa_handler = record_sig_handler;
>> @@ -588,10 +612,6 @@ record_wait (ptid_t ptid, struct target_
>>  	    }
>>  	  else
>>  	    {
>> -	      CORE_ADDR tmp_pc;
>> -	      struct bp_location *bl;
>> -	      struct breakpoint *b;
>> -
>>  	      if (record_debug > 1)
>>  		{
>>  		  fprintf_unfiltered (gdb_stdlog,
>> @@ -632,35 +652,24 @@ record_wait (ptid_t ptid, struct target_
>>  		    }
>>  
>>  		  /* check breakpoint */
>> -		  tmp_pc = read_pc ();
>> -		  for (bl = bp_location_chain; bl; bl = bl->global_next)
>> +		  tmp_pc = regcache_read_pc (regcache);
>> +		  if (breakpoint_inserted_here_p (tmp_pc))
>>  		    {
>> -		      b = bl->owner;
>> -		      gdb_assert (b);
>> -		      if (b->enable_state != bp_enabled
>> -			  && b->enable_state != bp_permanent)
>> -			continue;
>> -
>> -		      if (b->type == bp_watchpoint || b->type == bp_catch_fork
>> -			  || b->type == bp_catch_vfork
>> -			  || b->type == bp_catch_exec
>> -			  || b->type == bp_hardware_watchpoint
>> -			  || b->type == bp_read_watchpoint
>> -			  || b->type == bp_access_watchpoint)
>> +		      if (record_debug)
>>  			{
>> -			  continue;
>> +			  fprintf_unfiltered (gdb_stdlog,
>> +					      "Process record: break at 0x%s.\n",
>> +					      paddr_nz (tmp_pc));
>>  			}
>> -		      if (bl->address == tmp_pc)
>> +		      if (gdbarch_decr_pc_after_break (get_regcache_arch (regcache))
>> +			  && execution_direction == EXEC_FORWARD)
>>  			{
>> -			  if (record_debug)
>> -			    {
>> -			      fprintf_unfiltered (gdb_stdlog,
>> -						  "Process record: break at 0x%s.\n",
>> -						  paddr_nz (tmp_pc));
>> -			    }
>> -			  continue_flag = 0;
>> -			  break;
>> +			  regcache_write_pc (regcache,
>> +					     tmp_pc +
>> +					     gdbarch_decr_pc_after_break
>> +					     (get_regcache_arch (regcache)));
>>  			}
>> +		      continue_flag = 0;
>>  		    }
>>  		}
>>  	      if (execution_direction == EXEC_REVERSE)
>> @@ -691,6 +700,7 @@ next:
>>  	  perror_with_name (_("Process record: sigaction"));
>>  	}
>>  
>> +replay_out:
>>        if (record_get_sig)
>>  	{
>>  	  status->value.sig = TARGET_SIGNAL_INT;


  parent reply	other threads:[~2008-10-23 23:28 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-18  1:11 Pedro Alves
2008-10-18  1:26 ` Michael Snyder
2008-10-18  3:09   ` Pedro Alves
2008-10-18  3:18     ` teawater
2008-10-18  8:42     ` Andreas Schwab
2008-10-19 14:28       ` teawater
2008-10-19 20:10     ` Daniel Jacobowitz
2008-10-18  3:07 ` teawater
2008-10-18  3:26   ` Pedro Alves
2008-10-19 22:44 ` Michael Snyder
2008-10-20  0:10   ` Pedro Alves
2008-10-20  0:44     ` Michael Snyder
2008-10-20  1:46       ` Daniel Jacobowitz
2008-10-20 12:10       ` Pedro Alves
2008-10-20 15:50         ` teawater
2008-10-20 17:44       ` Pedro Alves
2008-10-20 17:51         ` Michael Snyder
2008-10-20 23:36           ` teawater
2008-10-21  0:21             ` Pedro Alves
2008-10-21  0:56               ` teawater
2008-10-21  3:13                 ` teawater
2008-10-21  6:52               ` teawater
2008-10-21  6:52                 ` teawater
2008-10-23 23:28                 ` Michael Snyder [this message]
2008-10-21  7:04               ` teawater
2008-10-21 18:36                 ` Michael Snyder
2008-10-22  0:39                   ` teawater
2008-10-23 23:32     ` Michael Snyder
2008-10-23 23:46       ` Pedro Alves
2008-10-23 23:55         ` Pedro Alves
2008-10-24  0:45           ` Michael Snyder
2008-10-24  0:43         ` Michael Snyder
2008-10-24  1:51           ` Pedro Alves
2008-10-24  8:11             ` teawater
2008-10-24  9:58               ` teawater
2008-10-25  7:08                 ` teawater
2008-10-28  3:21                   ` teawater
2008-10-29  1:24                   ` Michael Snyder
2008-10-30  3:01                     ` teawater
2008-10-30 12:21                     ` Pedro Alves
2008-10-30 22:06                       ` Michael Snyder
2008-10-30 21:44                         ` Pedro Alves
2008-10-30 21:29                           ` Michael Snyder
2008-10-31 13:04                           ` teawater
2008-10-31  0:25                       ` teawater

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=4901076C.8040104@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=teawater@gmail.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