Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] register_modified_event
Date: Mon, 19 Aug 2002 15:17:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0208191515430.9079-100000@valrhona.uglyboxes.com> (raw)

Hi,

Here's another event fallout from Apple's MI work. This defines a new 
event (and adds two notifications for it), register_modified_event, which 
is sent whenever a register is modified (usually by a user in the command 
line, but could be via MI or varobj, etc).

As expected, this causes no regressions in the testsuite. I have tests for 
this, but I can't commit any of them until all my MI stuff is complete, 
since event notifications in MI are quite new (and still in approval 
process).

Keith

PS. FYI, I would have named it register_changed_event, just like the hook, 
but there is a name conflict with register_changed in regcache.c.

ChangeLog
2002-08-18  Keith Seitz  <keiths@redhat.com>

        * gdb-events.sh: Add selected_frame_level_changed event.
        * gdb-events.c: Regenerated.
        * gdb-events.c: Regenerated.
        * valops.c (value_assign): Add register_update event notification
        for lval_register and lval_reg_frame_relative.

Patch
Index: gdb-events.sh
===================================================================
RCS file: /cvs/src/src/gdb/gdb-events.sh,v
retrieving revision 1.13
diff -p -r1.13 gdb-events.sh
*** gdb-events.sh	16 Aug 2002 16:09:07 -0000	1.13
--- gdb-events.sh	19 Aug 2002 22:11:13 -0000
*************** f:void:tracepoint_create:int number:numb
*** 65,70 ****
--- 65,71 ----
  f:void:tracepoint_delete:int number:number
  f:void:tracepoint_modify:int number:number
  f:void:architecture_changed:void
+ f:void:register_modified:int regno:regno
  #*:void:annotate_starting_hook:void
  #*:void:annotate_stopped_hook:void
  #*:void:annotate_signalled_hook:void
*************** f:void:architecture_changed:void
*** 87,93 ****
  #*:void:readline_begin_hook:char *format, ...:format
  #*:char *:readline_hook:char *prompt:prompt
  #*:void:readline_end_hook:void
- #*:void:register_changed_hook:int regno:regno
  #*:void:memory_changed_hook:CORE_ADDR addr, int len:addr, len
  #*:void:context_hook:int num:num
  #*:int:target_wait_hook:int pid, struct target_waitstatus *status:pid, status
--- 88,93 ----
Index: valops.c
===================================================================
RCS file: /cvs/src/src/gdb/valops.c,v
retrieving revision 1.66
diff -p -r1.66 valops.c
*** valops.c	1 Aug 2002 17:18:33 -0000	1.66
--- valops.c	19 Aug 2002 22:11:41 -0000
*************** value_assign (struct value *toval, struc
*** 678,683 ****
--- 678,686 ----
  			      VALUE_CONTENTS (fromval), TYPE_LENGTH (type));
  #endif
  	}
+ 
+       register_modified_event (VALUE_REGNO (toval));
+ 
        /* Assigning to the stack pointer, frame pointer, and other
           (architecture and calling convention specific) registers may
           cause the frame cache to be out of date.  We just do this
*************** value_assign (struct value *toval, struc
*** 765,770 ****
--- 768,774 ----
  
  	if (register_changed_hook)
  	  register_changed_hook (-1);
+ 	register_modified_event (regno);
        }
        break;
  


             reply	other threads:[~2002-08-19 22:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-19 15:17 Keith Seitz [this message]
2002-08-19 15:49 ` Andrew Cagney
2002-08-20  9:36   ` Keith Seitz
2002-08-20 13:46     ` Andrew Cagney
2002-08-20 15:36       ` Keith Seitz
2002-08-20 17:23         ` Andrew Cagney
2002-08-21  8:34           ` Keith Seitz

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=Pine.LNX.4.44.0208191515430.9079-100000@valrhona.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=gdb-patches@sources.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