[PATCH v2 04/36] Guile extension language: breakpoint.c changes
Doug Evans
xdje42@gmail.com
Mon Jan 20 21:53:00 GMT 2014
One can examine breakpoints from Python and then from Guile,
so we need to keep a copy of both underlying objects in the breakpoint.
The Guile object (scm_bp_object) is only created on demand,
so setting aside the additional member, there is no cost if Guile
isn't used.
2014-01-20 Doug Evans <xdje42@gmail.com>
* breakpoint.c (condition_command): Tweak comment to include Scheme.
* breakpoint.h (gdbscm_breakpoint_object): Add forward decl.
(struct breakpoint): New member scm_bp_object.
diff --git a/gdb/breakpoint.h b/gdb/breakpoint.h
index 8a5c4e8..4be9f23 100644
--- a/gdb/breakpoint.h
+++ b/gdb/breakpoint.h
@@ -29,6 +29,7 @@
struct value;
struct block;
struct gdbpy_breakpoint_object;
+struct gdbscm_breakpoint_object;
struct get_number_or_range_state;
struct thread_info;
struct bpstats;
@@ -739,6 +740,9 @@ struct breakpoint
can sometimes be NULL for enabled GDBs as not all breakpoint
types are tracked by the scripting language API. */
struct gdbpy_breakpoint_object *py_bp_object;
+
+ /* Same as py_bp_object, but for Scheme. */
+ struct gdbscm_breakpoint_object *scm_bp_object;
};
/* An instance of this type is used to represent a watchpoint. It
More information about the Gdb-patches
mailing list