From: Keith Seitz <keiths@cygnus.com>
To: Insight Maling List <insight@sources.redhat.com>
Subject: Breakpoint/Tracepoint Events checked in
Date: Thu, 19 Apr 2001 15:54:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.91.1010419155205.12804O@ryobi.cygnus.com> (raw)
I've just committed changes which cause Insight to use the new event
model for breakpoint and tracepoint notifications.
This affects the source window (via SrcTextWin) and the breakpoint
window.
Please let me know if there are any difficulties encountered with this.
Keith
CVSROOT: /cvs/src
Module name: src
Changes by: kseitz@sources.redhat.com 2001-04-19 15:51:02
Modified files:
gdb/gdbtk : ChangeLog
gdb/gdbtk/generic: gdbtk-cmds.c gdbtk-hooks.c
gdb/gdbtk/library: bpwin.itb bpwin.ith srctextwin.itb
srctextwin.ith interface.tcl
Log message:
Breakpoint/tracepoint event notification using new event model...
* generic/gdbtk-cmds.c (gdb_set_bp): Use create_breakpoint_hook
to notify gui of changes.
(gdb_set_bp_addr): Ditto.
(gdb_get_breakpoint_info): Update comments to match reality.
* generic/gdbtk-hooks.c (breakpoint_notify): Only pass the
breakpoint number which generated the event.
(tracepoint_notify): Ditto for tracepoints.
* library/interface.tcl (gdb_breakpoint_change_hook): Mark
as deprecated and comment out definition.
(gdbtk_tcl_breakpoint): Use new GDBEvent event "breakpoint"
to notify rest of UI about breakpoint event.
(gdbtk_tcl_tracepoint): Ditto for "tracepoint" event.
* library/bpwin.ith (update): Renamed to "breakpoint".
(breakpoint): New public method.
(tracepoint): New public method.
(bp_add): Take event as argument instead of number.
(bp_modify): Ditto.
(bp_delete): Ditto.
* library/bpwin.itb (constructor): Remove
gdb_breakpoint_changed_hook.
(destructor): Ditto.
(build_win): Insert any existing breakpoints by
making BreakpointEvents for them.
(breakpoint): Renamed from "update" to handle
breakpoint events.
Remove code to deal with tracepoints.
(tracepoint): New method to handle tracepoint
events.
(bp_add): Deal with breakpoint events, not breakpoint
numbers.
(bp_modify): Ditto.
(bp_delete): Ditto.
* library/srctextwin.ith: Inherit from GDBWin.
(breakpoint): New public method.
(tracepoint): New public method.
* library/srctextwin.itb (constructor): Remove
gdb_breakpoint_changed_hook.
(destructor): Ditto.
(breakpoint): New method to handle breakpoint event.
(tracepoint): New method to handle tracepoint event.
(do_bp): Handle duplicate breakpoints for asm, too.
(remove_bp_at_line): Delete breakpoints by number, not
linespec. clear_command removes breakpoints from the
breakpoint_chain BEFORE deleting the breakpoint. delete_command
does this afterward (so we can call gdb_get_breakpoint_info on
an about-to-be-deleted breakpoint).
Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/gdbtk/ChangeLog.diff?cvsroot=src&r1=1.64&r2=1.65
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/gdbtk/generic/gdbtk-cmds.c.diff?cvsroot=src&r1=1.30&r2=1.31
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/gdbtk/generic/gdbtk-hooks.c.diff?cvsroot=src&r1=1.9&r2=1.10
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/gdbtk/library/bpwin.itb.diff?cvsroot=src&r1=1.4&r2=1.5
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/gdbtk/library/bpwin.ith.diff?cvsroot=src&r1=1.1.1.1&r2=1.2
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/gdbtk/library/srctextwin.itb.diff?cvsroot=src&r1=1.22&r2=1.23
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/gdbtk/library/srctextwin.ith.diff?cvsroot=src&r1=1.10&r2=1.11
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/gdbtk/library/interface.tcl.diff?cvsroot=src&r1=1.17&r2=1.18
reply other threads:[~2001-04-19 15:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.SOL.3.91.1010419155205.12804O@ryobi.cygnus.com \
--to=keiths@cygnus.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).