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] gdb-events.sh: Add clear_gdb_event_hooks
Date: Wed, 14 Aug 2002 15:37:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0208141529490.1407-100000@valrhona.uglyboxes.com> (raw)

Hi,

More fallout of my MI work: when switching interpreters, we'll need to be 
able to clear all hooks and event handlers so that when the new 
interpreter's hooks/event handlers are installed, we don't leave the old 
ones lying about.

Ok?
Keith

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

        * gdb-events.sh (clear_gdb_event_hooks): New function.
        * gdb-events.c: Regenerate.
        * gdb-events.h: Regenerate.

Patch
Index: gdb-events.sh
===================================================================
RCS file: /cvs/src/src/gdb/gdb-events.sh,v
retrieving revision 1.12
retrieving revision 1.12.6.1
diff -p -r1.12 -r1.12.6.1
*** gdb-events.sh	19 Mar 2002 02:51:05 -0000	1.12
--- gdb-events.sh	24 Jun 2002 23:59:57 -0000	1.12.6.1
*************** extern struct gdb_events *set_gdb_event_
*** 267,272 ****
--- 267,275 ----
  /* Deliver any pending events. */
  extern void gdb_events_deliver (struct gdb_events *vector);
  
+ /* Clear event handlers */
+ extern void clear_gdb_event_hooks (void);
+ 
  #if !WITH_GDB_EVENTS
  #define set_gdb_events(x) 0
  #define set_gdb_event_hooks(x) 0
*************** do
*** 389,394 ****
--- 392,409 ----
    esac
  done
  cat <<EOF
+ }
+ #endif
+ EOF
+ 
+ # Clear hooks function
+ echo ""
+ cat <<EOF
+ #if WITH_GDB_EVENTS
+ void
+ clear_gdb_event_hooks (void)
+ {
+   set_gdb_event_hooks (&null_event_hooks);
  }
  #endif
  EOF


             reply	other threads:[~2002-08-14 22:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-14 15:37 Keith Seitz [this message]
2002-08-16  7:05 ` Andrew Cagney
2002-08-16  9:09   ` 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.0208141529490.1407-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