X-Git-Url: http://git.efficios.com/?a=blobdiff_plain;f=gdb%2Fbreakpoint.h;h=a957b6f3cd5baaffc940b87027ff327209f9b1e7;hb=edf0c1b7caed4e2bfb9a84fd9c226c6720da1d97;hp=98a7157ea10e4c153b7dc6aa2818259aafa206e4;hpb=aa7d318d60c595f97230f45575c882c73f7bdcf7;p=deliverable%2Fbinutils-gdb.git diff --git a/gdb/breakpoint.h b/gdb/breakpoint.h index 98a7157ea1..a957b6f3cd 100644 --- a/gdb/breakpoint.h +++ b/gdb/breakpoint.h @@ -1,6 +1,5 @@ /* Data structures associated with breakpoints in GDB. - Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, - 2002, 2003, 2004, 2007, 2008, 2009, 2010 Free Software Foundation, Inc. + Copyright (C) 1992-2004, 2007-2012 Free Software Foundation, Inc. This file is part of GDB. @@ -23,28 +22,37 @@ #include "frame.h" #include "value.h" #include "vec.h" +#include "ax.h" struct value; struct block; - -/* This is the maximum number of bytes a breakpoint instruction can take. - Feel free to increase it. It's just used in a few places to size - arrays that should be independent of the target architecture. */ +struct breakpoint_object; +struct get_number_or_range_state; +struct thread_info; +struct bpstats; +struct bp_location; +struct linespec_result; +struct linespec_sals; + +/* This is the maximum number of bytes a breakpoint instruction can + take. Feel free to increase it. It's just used in a few places to + size arrays that should be independent of the target + architecture. */ #define BREAKPOINT_MAX 16 /* Type of breakpoint. */ -/* FIXME In the future, we should fold all other breakpoint-like things into - here. This includes: +/* FIXME In the future, we should fold all other breakpoint-like + things into here. This includes: - * single-step (for machines where we have to simulate single stepping) - (probably, though perhaps it is better for it to look as much as - possible like a single-step to wait_for_inferior). */ + * single-step (for machines where we have to simulate single + stepping) (probably, though perhaps it is better for it to look as + much as possible like a single-step to wait_for_inferior). */ enum bptype { - bp_none = 0, /* Eventpoint has been deleted. */ + bp_none = 0, /* Eventpoint has been deleted */ bp_breakpoint, /* Normal breakpoint */ bp_hardware_breakpoint, /* Hardware assisted breakpoint */ bp_until, /* used by until command */ @@ -56,10 +64,21 @@ enum bptype bp_longjmp, /* secret breakpoint to find longjmp() */ bp_longjmp_resume, /* secret breakpoint to escape longjmp() */ - /* Used by wait_for_inferior for stepping over subroutine calls, for - stepping over signal handlers, and for skipping prologues. */ + /* An internal breakpoint that is installed on the unwinder's + debug hook. */ + bp_exception, + /* An internal breakpoint that is set at the point where an + exception will land. */ + bp_exception_resume, + + /* Used by wait_for_inferior for stepping over subroutine calls, + and for skipping prologues. */ bp_step_resume, + /* Used by wait_for_inferior for stepping over signal + handlers. */ + bp_hp_step_resume, + /* Used to detect when a watchpoint expression has gone out of scope. These breakpoints are usually not visible to the user. @@ -75,12 +94,13 @@ enum bptype bp_watchpoint_scope, /* The breakpoint at the end of a call dummy. */ - /* FIXME: What if the function we are calling longjmp()s out of the - call, or the user gets out with the "return" command? We currently - have no way of cleaning up the breakpoint in these (obscure) situations. - (Probably can solve this by noticing longjmp, "return", etc., it's - similar to noticing when a watchpoint on a local variable goes out - of scope (with hardware support for watchpoints)). */ + /* FIXME: What if the function we are calling longjmp()s out of + the call, or the user gets out with the "return" command? We + currently have no way of cleaning up the breakpoint in these + (obscure) situations. (Probably can solve this by noticing + longjmp, "return", etc., it's similar to noticing when a + watchpoint on a local variable goes out of scope (with hardware + support for watchpoints)). */ bp_call_dummy, /* A breakpoint set on std::terminate, that is used to catch @@ -125,48 +145,71 @@ enum bptype /* Master copies of std::terminate breakpoints. */ bp_std_terminate_master, + /* Like bp_longjmp_master, but for exceptions. */ + bp_exception_master, + bp_catchpoint, bp_tracepoint, bp_fast_tracepoint, + bp_static_tracepoint, + + /* A dynamic printf stops at the given location, does a formatted + print, then automatically continues. (Although this is sort of + like a macro packaging up standard breakpoint functionality, + GDB doesn't have a way to construct types of breakpoint from + elements of behavior.) */ + bp_dprintf, /* Event for JIT compiled code generation or deletion. */ bp_jit_event, + + /* Breakpoint is placed at the STT_GNU_IFUNC resolver. When hit GDB + inserts new bp_gnu_ifunc_resolver_return at the caller. + bp_gnu_ifunc_resolver is still being kept here as a different thread + may still hit it before bp_gnu_ifunc_resolver_return is hit by the + original thread. */ + bp_gnu_ifunc_resolver, + + /* On its hit GDB now know the resolved address of the target + STT_GNU_IFUNC function. Associated bp_gnu_ifunc_resolver can be + deleted now and the breakpoint moved to the target function entry + point. */ + bp_gnu_ifunc_resolver_return, }; -/* States of enablement of breakpoint. */ +/* States of enablement of breakpoint. */ enum enable_state { - bp_disabled, /* The eventpoint is inactive, and cannot trigger. */ - bp_enabled, /* The eventpoint is active, and can trigger. */ - bp_call_disabled, /* The eventpoint has been disabled while a call - into the inferior is "in flight", because some - eventpoints interfere with the implementation of - a call on some targets. The eventpoint will be - automatically enabled and reset when the call - "lands" (either completes, or stops at another - eventpoint). */ - bp_startup_disabled,/* The eventpoint has been disabled during inferior - startup. This is necessary on some targets where - the main executable will get relocated during - startup, making breakpoint addresses invalid. - The eventpoint will be automatically enabled and - reset once inferior startup is complete. */ - bp_permanent /* There is a breakpoint instruction hard-wired into - the target's code. Don't try to write another - breakpoint instruction on top of it, or restore - its value. Step over it using the architecture's - SKIP_INSN macro. */ + bp_disabled, /* The eventpoint is inactive, and cannot + trigger. */ + bp_enabled, /* The eventpoint is active, and can + trigger. */ + bp_call_disabled, /* The eventpoint has been disabled while a + call into the inferior is "in flight", + because some eventpoints interfere with + the implementation of a call on some + targets. The eventpoint will be + automatically enabled and reset when the + call "lands" (either completes, or stops + at another eventpoint). */ + bp_permanent /* There is a breakpoint instruction + hard-wired into the target's code. Don't + try to write another breakpoint + instruction on top of it, or restore its + value. Step over it using the + architecture's SKIP_INSN macro. */ }; -/* Disposition of breakpoint. Ie: what to do after hitting it. */ +/* Disposition of breakpoint. Ie: what to do after hitting it. */ enum bpdisp { disp_del, /* Delete it */ - disp_del_at_next_stop, /* Delete at next stop, whether hit or not */ + disp_del_at_next_stop, /* Delete at next stop, + whether hit or not */ disp_disable, /* Disable it */ disp_donttouch /* Leave it alone */ }; @@ -180,6 +223,16 @@ enum target_hw_bp_type }; +/* Status of breakpoint conditions used when synchronizing + conditions with the target. */ + +enum condition_status + { + condition_unchanged = 0, + condition_modified, + condition_updated + }; + /* Information used by targets to insert and remove breakpoints. */ struct bp_target_info @@ -194,6 +247,10 @@ struct bp_target_info is used to determine the type of breakpoint to insert. */ CORE_ADDR placed_address; + /* If this is a ranged breakpoint, then this field contains the + length of the range that will be watched for execution. */ + int length; + /* If the breakpoint lives in memory and reading that memory would give back the breakpoint, instead of the original contents, then the original contents are cached here. Only SHADOW_LEN bytes of @@ -204,12 +261,16 @@ struct bp_target_info int shadow_len; /* The size of the placed breakpoint, according to - gdbarch_breakpoint_from_pc, when the breakpoint was inserted. This is - generally the same as SHADOW_LEN, unless we did not need + gdbarch_breakpoint_from_pc, when the breakpoint was inserted. + This is generally the same as SHADOW_LEN, unless we did not need to read from the target to implement the memory breakpoint - (e.g. if a remote stub handled the details). We may still - need the size to remove the breakpoint safely. */ + (e.g. if a remote stub handled the details). We may still need + the size to remove the breakpoint safely. */ int placed_size; + + /* Vector of conditions the target should evaluate if it supports target-side + breakpoint conditions. */ + VEC(agent_expr_p) *conditions; }; /* GDB maintains two types of information about each breakpoint (or @@ -233,18 +294,38 @@ enum bp_loc_type bp_loc_other /* Miscellaneous... */ }; +/* This structure is a collection of function pointers that, if + available, will be called instead of performing the default action + for this bp_loc_type. */ + +struct bp_location_ops +{ + /* Destructor. Releases everything from SELF (but not SELF + itself). */ + void (*dtor) (struct bp_location *self); +}; + struct bp_location { /* Chain pointer to the next breakpoint location for the same parent breakpoint. */ struct bp_location *next; + /* Methods associated with this location. */ + const struct bp_location_ops *ops; + + /* The reference count. */ + int refc; + /* Type of this breakpoint location. */ enum bp_loc_type loc_type; /* Each breakpoint location must belong to exactly one higher-level - breakpoint. This and the DUPLICATE flag are more straightforward - than reference counting. */ + breakpoint. This pointer is NULL iff this bp_location is no + longer attached to a breakpoint. For example, when a breakpoint + is deleted, its locations may still be found in the + moribund_locations list, or if we had stopped for it, in + bpstats. */ struct breakpoint *owner; /* Conditional. Break only if this expression's value is nonzero. @@ -256,6 +337,30 @@ struct bp_location the owner breakpoint object. */ struct expression *cond; + /* Conditional expression in agent expression + bytecode form. This is used for stub-side breakpoint + condition evaluation. */ + struct agent_expr *cond_bytecode; + + /* Signals that the condition has changed since the last time + we updated the global location list. This means the condition + needs to be sent to the target again. This is used together + with target-side breakpoint conditions. + + condition_unchanged: It means there has been no condition changes. + + condition_modified: It means this location had its condition modified. + + condition_updated: It means we already marked all the locations that are + duplicates of this location and thus we don't need to call + force_breakpoint_reinsertion (...) for this location. */ + + enum condition_status condition_changed; + + /* Signals that breakpoint conditions need to be re-synched with the + target. This has no use other than target-side breakpoints. */ + char needs_update; + /* This location's address is in an unloaded solib, and so this location should not be inserted. It will be automatically enabled when that solib is loaded. */ @@ -268,7 +373,11 @@ struct bp_location char inserted; /* Nonzero if this is not the first breakpoint in the list - for the given address. */ + for the given address. location of tracepoint can _never_ + be duplicated with other locations of tracepoints and other + kinds of breakpoints, because two locations at the same + address may have different actions, so both of these locations + should be downloaded and so that `tfind N' always works. */ char duplicate; /* If we someday support real thread-specific breakpoints, then @@ -295,14 +404,17 @@ struct bp_location bp_loc_other. */ CORE_ADDR address; - /* For hardware watchpoints, the size of data ad ADDRESS being watches. */ + /* For hardware watchpoints, the size of the memory region being + watched. For hardware ranged breakpoints, the size of the + breakpoint range. */ int length; - /* Type of hardware watchpoint. */ + /* Type of hardware watchpoint. */ enum target_hw_bp_type watchpoint_type; /* For any breakpoint type with an address, this is the section - associated with the address. Used primarily for overlay debugging. */ + associated with the address. Used primarily for overlay + debugging. */ struct obj_section *section; /* Address at which breakpoint was requested, either by the user or @@ -313,6 +425,15 @@ struct bp_location processor's architectual constraints. */ CORE_ADDR requested_address; + /* An additional address assigned with this location. This is currently + only used by STT_GNU_IFUNC resolver breakpoints to hold the address + of the resolver function. */ + CORE_ADDR related_address; + + /* If the location comes from a probe point, this is the probe associated + with it. */ + struct probe *probe; + char *function_name; /* Details of the placed breakpoint, when inserted. */ @@ -331,39 +452,141 @@ struct bp_location This variable keeps a number of events still to go, when it becomes 0 this location is retired. */ int events_till_retirement; + + /* Line number of this address. */ + + int line_number; + + /* Source file name of this address. */ + + char *source_file; }; /* This structure is a collection of function pointers that, if available, will be called instead of the performing the default action for this bptype. */ -struct breakpoint_ops +struct breakpoint_ops { - /* Insert the breakpoint or activate the catchpoint. Should raise - an exception if the operation failed. */ - void (*insert) (struct breakpoint *); + /* Destructor. Releases everything from SELF (but not SELF + itself). */ + void (*dtor) (struct breakpoint *self); - /* Remove the breakpoint/catchpoint that was previously inserted - with the "insert" method above. Return non-zero if the operation - succeeded. */ - int (*remove) (struct breakpoint *); + /* Allocate a location for this breakpoint. */ + struct bp_location * (*allocate_location) (struct breakpoint *); + + /* Reevaluate a breakpoint. This is necessary after symbols change + (e.g., an executable or DSO was loaded, or the inferior just + started). */ + void (*re_set) (struct breakpoint *self); - /* Return non-zero if the debugger should tell the user that this - breakpoint was hit. */ - int (*breakpoint_hit) (struct breakpoint *); + /* Insert the breakpoint or watchpoint or activate the catchpoint. + Return 0 for success, 1 if the breakpoint, watchpoint or + catchpoint type is not supported, -1 for failure. */ + int (*insert_location) (struct bp_location *); + + /* Remove the breakpoint/catchpoint that was previously inserted + with the "insert" method above. Return 0 for success, 1 if the + breakpoint, watchpoint or catchpoint type is not supported, + -1 for failure. */ + int (*remove_location) (struct bp_location *); + + /* Return true if it the target has stopped due to hitting + breakpoint location BL. This function does not check if we + should stop, only if BL explains the stop. ASPACE is the address + space in which the event occurred, BP_ADDR is the address at + which the inferior stopped, and WS is the target_waitstatus + describing the event. */ + int (*breakpoint_hit) (const struct bp_location *bl, + struct address_space *aspace, + CORE_ADDR bp_addr, + const struct target_waitstatus *ws); + + /* Check internal conditions of the breakpoint referred to by BS. + If we should not stop for this breakpoint, set BS->stop to 0. */ + void (*check_status) (struct bpstats *bs); + + /* Tell how many hardware resources (debug registers) are needed + for this breakpoint. If this function is not provided, then + the breakpoint or watchpoint needs one debug register. */ + int (*resources_needed) (const struct bp_location *); + + /* Tell whether we can downgrade from a hardware watchpoint to a software + one. If not, the user will not be able to enable the watchpoint when + there are not enough hardware resources available. */ + int (*works_in_software_mode) (const struct breakpoint *); /* The normal print routine for this breakpoint, called when we hit it. */ - enum print_stop_action (*print_it) (struct breakpoint *); + enum print_stop_action (*print_it) (struct bpstats *bs); - /* Display information about this breakpoint, for "info breakpoints". */ + /* Display information about this breakpoint, for "info + breakpoints". */ void (*print_one) (struct breakpoint *, struct bp_location **); - /* Display information about this breakpoint after setting it (roughly - speaking; this is called from "mention"). */ + /* Display extra information about this breakpoint, below the normal + breakpoint description in "info breakpoints". + + In the example below, the "address range" line was printed + by print_one_detail_ranged_breakpoint. + + (gdb) info breakpoints + Num Type Disp Enb Address What + 2 hw breakpoint keep y in main at test-watch.c:70 + address range: [0x10000458, 0x100004c7] + + */ + void (*print_one_detail) (const struct breakpoint *, struct ui_out *); + + /* Display information about this breakpoint after setting it + (roughly speaking; this is called from "mention"). */ void (*print_mention) (struct breakpoint *); + + /* Print to FP the CLI command that recreates this breakpoint. */ + void (*print_recreate) (struct breakpoint *, struct ui_file *fp); + + /* Create SALs from address string, storing the result in linespec_result. + + For an explanation about the arguments, see the function + `create_sals_from_address_default'. + + This function is called inside `create_breakpoint'. */ + void (*create_sals_from_address) (char **, struct linespec_result *, + enum bptype, char *, char **); + + /* This method will be responsible for creating a breakpoint given its SALs. + Usually, it just calls `create_breakpoints_sal' (for ordinary + breakpoints). However, there may be some special cases where we might + need to do some tweaks, e.g., see + `strace_marker_create_breakpoints_sal'. + + This function is called inside `create_breakpoint'. */ + void (*create_breakpoints_sal) (struct gdbarch *, + struct linespec_result *, + struct linespec_sals *, char *, + char *, + enum bptype, enum bpdisp, int, int, + int, const struct breakpoint_ops *, + int, int, int, unsigned); + + /* Given the address string (second parameter), this method decodes it + and provides the SAL locations related to it. For ordinary breakpoints, + it calls `decode_line_full'. + + This function is called inside `addr_string_to_sals'. */ + void (*decode_linespec) (struct breakpoint *, char **, + struct symtabs_and_lines *); }; +/* Helper for breakpoint_ops->print_recreate implementations. Prints + the "thread" or "task" condition of B, and then a newline. + + Necessary because most breakpoint implementations accept + thread/task conditions at the end of the spec line, like "break foo + thread 1", which needs outputting before any breakpoint-type + specific extra command necessary for B's recreation. */ +extern void print_recreate_thread (struct breakpoint *b, struct ui_file *fp); + enum watchpoint_triggered { /* This watchpoint definitely did not trigger. */ @@ -377,22 +600,20 @@ enum watchpoint_triggered watch_triggered_yes }; -/* This is used to declare the VEC syscalls_to_be_caught. */ -DEF_VEC_I(int); - typedef struct bp_location *bp_location_p; DEF_VEC_P(bp_location_p); /* A reference-counted struct command_line. This lets multiple - breakpoints share a single command list. */ -struct counted_command_line -{ - /* The reference count. */ - int refc; + breakpoints share a single command list. This is an implementation + detail to the breakpoints module. */ +struct counted_command_line; - /* The command list. */ - struct command_line *commands; -}; +/* Some targets (e.g., embedded PowerPC) need two debug registers to set + a watchpoint over a memory region. If this flag is true, GDB will use + only one register per watchpoint, thus assuming that all acesses that + modify a memory location happen at its starting address. */ + +extern int target_exact_watchpoints; /* Note that the ->silent field is not currently used by any commands (though the code is in there if it was to be, and set_raw_breakpoint @@ -400,16 +621,19 @@ struct counted_command_line useful for a hack I had to put in; I'm going to leave it in because I can see how there might be times when it would indeed be useful */ -/* This is for a breakpoint or a watchpoint. */ +/* This is for all kinds of breakpoints. */ struct breakpoint { + /* Methods associated with this breakpoint. */ + const struct breakpoint_ops *ops; + struct breakpoint *next; - /* Type of breakpoint. */ + /* Type of breakpoint. */ enum bptype type; /* Zero means disabled; remember the info but don't break here. */ enum enable_state enable_state; - /* What to do with this breakpoint after we hit it. */ + /* What to do with this breakpoint after we hit it. */ enum bpdisp disposition; /* Number assigned to distinguish breakpoints. */ int number; @@ -417,85 +641,69 @@ struct breakpoint /* Location(s) associated with this high-level breakpoint. */ struct bp_location *loc; - /* Line number of this address. */ - - int line_number; - - /* Source file name of this address. */ - - char *source_file; - /* Non-zero means a silent breakpoint (don't print frame info - if we stop here). */ + if we stop here). */ unsigned char silent; + /* Non-zero means display ADDR_STRING to the user verbatim. */ + unsigned char display_canonical; /* Number of stops at this breakpoint that should be continued automatically before really stopping. */ int ignore_count; - /* Chain of command lines to execute when this breakpoint is hit. */ + + /* Number of stops at this breakpoint before it will be + disabled. */ + int enable_count; + + /* Chain of command lines to execute when this breakpoint is + hit. */ struct counted_command_line *commands; /* Stack depth (address of frame). If nonzero, break only if fp equals this. */ struct frame_id frame_id; - /* The program space used to set the breakpoint. */ + /* The program space used to set the breakpoint. This is only set + for breakpoints which are specific to a program space; for + non-thread-specific ordinary breakpoints this is NULL. */ struct program_space *pspace; /* String we used to set the breakpoint (malloc'd). */ char *addr_string; + + /* The filter that should be passed to decode_line_full when + re-setting this breakpoint. This may be NULL, but otherwise is + allocated with xmalloc. */ + char *filter; + + /* For a ranged breakpoint, the string we used to find + the end of the range (malloc'd). */ + char *addr_string_range_end; + /* Architecture we used to set the breakpoint. */ struct gdbarch *gdbarch; /* Language we used to set the breakpoint. */ enum language language; /* Input radix we used to set the breakpoint. */ int input_radix; - /* String form of the breakpoint condition (malloc'd), or NULL if there - is no condition. */ + /* String form of the breakpoint condition (malloc'd), or NULL if + there is no condition. */ char *cond_string; - /* String form of exp (malloc'd), or NULL if none. */ - char *exp_string; - - /* The expression we are watching, or NULL if not a watchpoint. */ - struct expression *exp; - /* The largest block within which it is valid, or NULL if it is - valid anywhere (e.g. consists just of global symbols). */ - struct block *exp_valid_block; - /* The conditional expression if any. NULL if not a watchpoint. */ - struct expression *cond_exp; - /* The largest block within which it is valid, or NULL if it is - valid anywhere (e.g. consists just of global symbols). */ - struct block *cond_exp_valid_block; - /* Value of the watchpoint the last time we checked it, or NULL - when we do not know the value yet or the value was not - readable. VAL is never lazy. */ - struct value *val; - /* Nonzero if VAL is valid. If VAL_VALID is set but VAL is NULL, - then an error occurred reading the value. */ - int val_valid; + + /* String form of extra parameters, or NULL if there are none. */ + char *extra_string; /* Holds the address of the related watchpoint_scope breakpoint - when using watchpoints on local variables (might the concept - of a related breakpoint be useful elsewhere, if not just call - it the watchpoint_scope breakpoint or something like that. FIXME). */ + when using watchpoints on local variables (might the concept of + a related breakpoint be useful elsewhere, if not just call it + the watchpoint_scope breakpoint or something like that. + FIXME). */ struct breakpoint *related_breakpoint; - /* Holds the frame address which identifies the frame this - watchpoint should be evaluated in, or `null' if the watchpoint - should be evaluated on the outermost frame. */ - struct frame_id watchpoint_frame; - - /* Holds the thread which identifies the frame this watchpoint - should be considered in scope for, or `null_ptid' if the - watchpoint should be evaluated in all threads. */ - ptid_t watchpoint_thread; - - /* For hardware watchpoints, the triggered status according to the - hardware. */ - enum watchpoint_triggered watchpoint_triggered; - - /* Thread number for thread-specific breakpoint, or -1 if don't care. */ + /* Thread number for thread-specific breakpoint, + or -1 if don't care. */ int thread; - /* Ada task number for task-specific breakpoint, or 0 if don't care. */ + /* Ada task number for task-specific breakpoint, + or 0 if don't care. */ int task; /* Count of the number of times this breakpoint was taken, dumped @@ -504,41 +712,118 @@ struct breakpoint aborting, so you can back up to just before the abort. */ int hit_count; - /* Process id of a child process whose forking triggered this - catchpoint. This field is only valid immediately after this - catchpoint has triggered. */ - ptid_t forked_inferior_pid; - - /* Filename of a program whose exec triggered this catchpoint. - This field is only valid immediately after this catchpoint has - triggered. */ - char *exec_pathname; - - /* Syscall numbers used for the 'catch syscall' feature. - If no syscall has been specified for filtering, its value is NULL. - Otherwise, it holds a list of all syscalls to be caught. - The list elements are allocated with xmalloc. */ - VEC(int) *syscalls_to_be_caught; - - /* Methods associated with this breakpoint. */ - struct breakpoint_ops *ops; - /* Is breakpoint's condition not yet parsed because we found no location initially so had no context to parse the condition in. */ int condition_not_parsed; - /* Number of times this tracepoint should single-step - and collect additional data. */ - long step_count; + /* With a Python scripting enabled GDB, store a reference to the + Python object that has been associated with this breakpoint. + This is always NULL for a GDB that is not script enabled. It + can sometimes be NULL for enabled GDBs as not all breakpoint + types are tracked by the Python scripting API. */ + struct breakpoint_object *py_bp_object; + }; - /* Number of times this tracepoint should be hit before - disabling/ending. */ - int pass_count; +/* An instance of this type is used to represent a watchpoint. It + includes a "struct breakpoint" as a kind of base class; users + downcast to "struct breakpoint *" when needed. */ - /* The number of the tracepoint on the target. */ - int number_on_target; - }; +struct watchpoint +{ + /* The base class. */ + struct breakpoint base; + + /* String form of exp to use for displaying to the user (malloc'd), + or NULL if none. */ + char *exp_string; + /* String form to use for reparsing of EXP (malloc'd) or NULL. */ + char *exp_string_reparse; + + /* The expression we are watching, or NULL if not a watchpoint. */ + struct expression *exp; + /* The largest block within which it is valid, or NULL if it is + valid anywhere (e.g. consists just of global symbols). */ + struct block *exp_valid_block; + /* The conditional expression if any. */ + struct expression *cond_exp; + /* The largest block within which it is valid, or NULL if it is + valid anywhere (e.g. consists just of global symbols). */ + struct block *cond_exp_valid_block; + /* Value of the watchpoint the last time we checked it, or NULL when + we do not know the value yet or the value was not readable. VAL + is never lazy. */ + struct value *val; + /* Nonzero if VAL is valid. If VAL_VALID is set but VAL is NULL, + then an error occurred reading the value. */ + int val_valid; + + /* Holds the frame address which identifies the frame this + watchpoint should be evaluated in, or `null' if the watchpoint + should be evaluated on the outermost frame. */ + struct frame_id watchpoint_frame; + + /* Holds the thread which identifies the frame this watchpoint + should be considered in scope for, or `null_ptid' if the + watchpoint should be evaluated in all threads. */ + ptid_t watchpoint_thread; + + /* For hardware watchpoints, the triggered status according to the + hardware. */ + enum watchpoint_triggered watchpoint_triggered; + + /* Whether this watchpoint is exact (see + target_exact_watchpoints). */ + int exact; + + /* The mask address for a masked hardware watchpoint. */ + CORE_ADDR hw_wp_mask; +}; + +/* Return true if BPT is either a software breakpoint or a hardware + breakpoint. */ + +extern int is_breakpoint (const struct breakpoint *bpt); + +/* Returns true if BPT is really a watchpoint. */ + +extern int is_watchpoint (const struct breakpoint *bpt); + +/* An instance of this type is used to represent all kinds of + tracepoints. It includes a "struct breakpoint" as a kind of base + class; users downcast to "struct breakpoint *" when needed. */ + +struct tracepoint +{ + /* The base class. */ + struct breakpoint base; + + /* Number of times this tracepoint should single-step and collect + additional data. */ + long step_count; + + /* Number of times this tracepoint should be hit before + disabling/ending. */ + int pass_count; + + /* The number of the tracepoint on the target. */ + int number_on_target; + + /* The total space taken by all the trace frames for this + tracepoint. */ + ULONGEST traceframe_usage; + + /* The static tracepoint marker id, if known. */ + char *static_trace_marker_id; + + /* LTTng/UST allow more than one marker with the same ID string, + although it unadvised because it confuses tools. When setting + static tracepoints by marker ID, this will record the index in + the array of markers we found for the given marker ID for which + this static tracepoint corresponds. When resetting breakpoints, + we will use this index to try to find the same marker again. */ + int static_trace_marker_id_idx; +}; typedef struct breakpoint *breakpoint_p; DEF_VEC_P(breakpoint_p); @@ -549,10 +834,6 @@ DEF_VEC_P(breakpoint_p); typedef struct bpstats *bpstat; -/* Frees any storage that is part of a bpstat. - Does not walk the 'next' chain. */ -extern void bpstat_free (bpstat); - /* Clears a chain of bpstat, freeing storage of each. */ extern void bpstat_clear (bpstat *); @@ -562,10 +843,24 @@ extern void bpstat_clear (bpstat *); extern bpstat bpstat_copy (bpstat); extern bpstat bpstat_stop_status (struct address_space *aspace, - CORE_ADDR pc, ptid_t ptid); + CORE_ADDR pc, ptid_t ptid, + const struct target_waitstatus *ws); /* This bpstat_what stuff tells wait_for_inferior what to do with a - breakpoint (a challenging task). */ + breakpoint (a challenging task). + + The enum values order defines priority-like order of the actions. + Once you've decided that some action is appropriate, you'll never + go back and decide something of a lower priority is better. Each + of these actions is mutually exclusive with the others. That + means, that if you find yourself adding a new action class here and + wanting to tell GDB that you have two simultaneous actions to + handle, something is wrong, and you probably don't actually need a + new action type. + + Note that a step resume breakpoint overrides another breakpoint of + signal handling (see comment in wait_for_inferior at where we set + the step_resume breakpoint). */ enum bpstat_what_main_action { @@ -574,28 +869,17 @@ enum bpstat_what_main_action else). */ BPSTAT_WHAT_KEEP_CHECKING, - /* Rather than distinguish between noisy and silent stops here, it - might be cleaner to have bpstat_print make that decision (also - taking into account stop_print_frame and source_only). But the - implications are a bit scary (interaction with auto-displays, etc.), - so I won't try it. */ - - /* Stop silently. */ - BPSTAT_WHAT_STOP_SILENT, - - /* Stop and print. */ - BPSTAT_WHAT_STOP_NOISY, - /* Remove breakpoints, single step once, then put them back in and - go back to what we were doing. It's possible that this should be - removed from the main_action and put into a separate field, to more - cleanly handle BPSTAT_WHAT_CLEAR_LONGJMP_RESUME_SINGLE. */ + go back to what we were doing. It's possible that this should + be removed from the main_action and put into a separate field, + to more cleanly handle + BPSTAT_WHAT_CLEAR_LONGJMP_RESUME_SINGLE. */ BPSTAT_WHAT_SINGLE, /* Set longjmp_resume breakpoint, remove all other breakpoints, - and continue. The "remove all other breakpoints" part is required - if we are also stepping over another breakpoint as well as doing - the longjmp handling. */ + and continue. The "remove all other breakpoints" part is + required if we are also stepping over another breakpoint as + well as doing the longjmp handling. */ BPSTAT_WHAT_SET_LONGJMP_RESUME, /* Clear longjmp_resume breakpoint, then handle as @@ -605,15 +889,26 @@ enum bpstat_what_main_action /* Clear step resume breakpoint, and keep checking. */ BPSTAT_WHAT_STEP_RESUME, - /* Check the dynamic linker's data structures for new libraries, then - keep checking. */ - BPSTAT_WHAT_CHECK_SHLIBS, + /* Rather than distinguish between noisy and silent stops here, it + might be cleaner to have bpstat_print make that decision (also + taking into account stop_print_frame and source_only). But the + implications are a bit scary (interaction with auto-displays, + etc.), so I won't try it. */ + + /* Stop silently. */ + BPSTAT_WHAT_STOP_SILENT, - /* Check for new JITed code. */ - BPSTAT_WHAT_CHECK_JIT, + /* Stop and print. */ + BPSTAT_WHAT_STOP_NOISY, - /* This is just used to keep track of how many enums there are. */ - BPSTAT_WHAT_LAST + /* Clear step resume breakpoint, and keep checking. High-priority + step-resume breakpoints are used when even if there's a user + breakpoint at the current PC when we set the step-resume + breakpoint, we don't want to re-handle any breakpoint other + than the step-resume when it's hit; instead we want to move + past the breakpoint. This is used in the case of skipping + signal handlers. */ + BPSTAT_WHAT_HP_STEP_RESUME, }; /* An enum indicating the kind of "stack dummy" stop. This is a bit @@ -634,40 +929,44 @@ struct bpstat_what { enum bpstat_what_main_action main_action; - /* Did we hit a call dummy breakpoint? This only goes with a main_action - of BPSTAT_WHAT_STOP_SILENT or BPSTAT_WHAT_STOP_NOISY (the concept of - continuing from a call dummy without popping the frame is not a - useful one). */ + /* Did we hit a call dummy breakpoint? This only goes with a + main_action of BPSTAT_WHAT_STOP_SILENT or + BPSTAT_WHAT_STOP_NOISY (the concept of continuing from a call + dummy without popping the frame is not a useful one). */ enum stop_stack_kind call_dummy; + + /* Used for BPSTAT_WHAT_SET_LONGJMP_RESUME and + BPSTAT_WHAT_CLEAR_LONGJMP_RESUME. True if we are handling a + longjmp, false if we are handling an exception. */ + int is_longjmp; }; /* The possible return values for print_bpstat, print_it_normal, - print_it_done, print_it_noop. */ + print_it_done, print_it_noop. */ enum print_stop_action { + /* We printed nothing or we need to do some more analysis. */ PRINT_UNKNOWN = -1, + + /* We printed something, and we *do* desire that something to be + followed by a location. */ PRINT_SRC_AND_LOC, + + /* We printed something, and we do *not* desire that something to + be followed by a location. */ PRINT_SRC_ONLY, + + /* We already printed all we needed to print, don't print anything + else. */ PRINT_NOTHING }; /* Tell what to do about this bpstat. */ struct bpstat_what bpstat_what (bpstat); -/* Find the bpstat associated with a breakpoint. NULL otherwise. */ +/* Find the bpstat associated with a breakpoint. NULL otherwise. */ bpstat bpstat_find_breakpoint (bpstat, struct breakpoint *); -/* Find a step_resume breakpoint associated with this bpstat. - (If there are multiple step_resume bp's on the list, this function - will arbitrarily pick one.) - - It is an error to use this function if BPSTAT doesn't contain a - step_resume breakpoint. - - See wait_for_inferior's use of this function. - */ -extern struct breakpoint *bpstat_find_step_resume_breakpoint (bpstat); - /* Nonzero if a signal that we got in wait() was due to circumstances explained by the BS. */ /* Currently that is true if we have hit a breakpoint, or if there is @@ -685,12 +984,13 @@ extern int bpstat_should_step (void); /* Print a message indicating what happened. Returns nonzero to say that only the source line should be printed after this (zero return means print the frame as well as the source line). */ -extern enum print_stop_action bpstat_print (bpstat); +extern enum print_stop_action bpstat_print (bpstat, int); + +/* Put in *NUM the breakpoint number of the first breakpoint we are + stopped at. *BSP upon return is a bpstat which points to the + remaining breakpoints stopped at (but which is not guaranteed to be + good for anything but further calls to bpstat_num). -/* Put in *NUM the breakpoint number of the first breakpoint we are stopped - at. *BSP upon return is a bpstat which points to the remaining - breakpoints stopped at (but which is not guaranteed to be good for - anything but further calls to bpstat_num). Return 0 if passed a bpstat which does not indicate any breakpoints. Return -1 if stopped at a breakpoint that has been deleted since we set it. @@ -703,20 +1003,23 @@ extern int bpstat_num (bpstat *, int *); command loop). */ extern void bpstat_do_actions (void); -/* Modify BS so that the actions will not be performed. */ -extern void bpstat_clear_actions (bpstat); +/* Modify all entries of STOP_BPSTAT of INFERIOR_PTID so that the actions will + not be performed. */ +extern void bpstat_clear_actions (void); /* Implementation: */ -/* Values used to tell the printing routine how to behave for this bpstat. */ +/* Values used to tell the printing routine how to behave for this + bpstat. */ enum bp_print_how { /* This is used when we want to do a normal printing of the reason - for stopping. The output will depend on the type of eventpoint - we are dealing with. This is the default value, most commonly - used. */ + for stopping. The output will depend on the type of eventpoint + we are dealing with. This is the default value, most commonly + used. */ print_it_normal, - /* This is used when nothing should be printed for this bpstat entry. */ + /* This is used when nothing should be printed for this bpstat + entry. */ print_it_noop, /* This is used when everything which needs to be printed has already been printed. But we still want to print the frame. */ @@ -725,16 +1028,37 @@ enum bp_print_how struct bpstats { - /* Linked list because there can be two breakpoints at the same - place, and a bpstat reflects the fact that both have been hit. */ + /* Linked list because there can be more than one breakpoint at + the same place, and a bpstat reflects the fact that all have + been hit. */ bpstat next; - /* Breakpoint that we are at. */ - const struct bp_location *breakpoint_at; + + /* Location that caused the stop. Locations are refcounted, so + this will never be NULL. Note that this location may end up + detached from a breakpoint, but that does not necessary mean + that the struct breakpoint is gone. E.g., consider a + watchpoint with a condition that involves an inferior function + call. Watchpoint locations are recreated often (on resumes, + hence on infcalls too). Between creating the bpstat and after + evaluating the watchpoint condition, this location may hence + end up detached from its original owner watchpoint, even though + the watchpoint is still listed. If it's condition evaluates as + true, we still want this location to cause a stop, and we will + still need to know which watchpoint it was originally attached. + What this means is that we should not (in most cases) follow + the `bpstat->bp_location->owner' link, but instead use the + `breakpoint_at' field below. */ + struct bp_location *bp_location_at; + + /* Breakpoint that caused the stop. This is nullified if the + breakpoint ends up being deleted. See comments on + `bp_location_at' above for why do we need this field instead of + following the location's owner. */ + struct breakpoint *breakpoint_at; + /* The associated command list. */ struct counted_command_line *commands; - /* Commands left to be done. This points somewhere in - base_command. */ - struct command_line *commands_left; + /* Old value associated with a watchpoint. */ struct value *old_val; @@ -769,15 +1093,18 @@ enum breakpoint_here /* Prototypes for breakpoint-related functions. */ -extern enum breakpoint_here breakpoint_here_p (struct address_space *, CORE_ADDR); +extern enum breakpoint_here breakpoint_here_p (struct address_space *, + CORE_ADDR); extern int moribund_breakpoint_here_p (struct address_space *, CORE_ADDR); extern int breakpoint_inserted_here_p (struct address_space *, CORE_ADDR); -extern int regular_breakpoint_inserted_here_p (struct address_space *, CORE_ADDR); +extern int regular_breakpoint_inserted_here_p (struct address_space *, + CORE_ADDR); -extern int software_breakpoint_inserted_here_p (struct address_space *, CORE_ADDR); +extern int software_breakpoint_inserted_here_p (struct address_space *, + CORE_ADDR); /* Returns true if there's a hardware watchpoint or access watchpoint inserted in the range defined by ADDR and LEN. */ @@ -785,10 +1112,21 @@ extern int hardware_watchpoint_inserted_in_range (struct address_space *, CORE_ADDR addr, ULONGEST len); -extern int breakpoint_thread_match (struct address_space *, CORE_ADDR, ptid_t); +extern int breakpoint_thread_match (struct address_space *, + CORE_ADDR, ptid_t); extern void until_break_command (char *, int, int); +/* Initialize a struct bp_location. */ + +extern void init_bp_location (struct bp_location *loc, + const struct bp_location_ops *ops, + struct breakpoint *owner); + +extern void update_breakpoint_locations (struct breakpoint *b, + struct symtabs_and_lines sals, + struct symtabs_and_lines sals_end); + extern void breakpoint_re_set (void); extern void breakpoint_re_set_thread (struct breakpoint *); @@ -803,9 +1141,6 @@ extern struct breakpoint *clone_momentary_breakpoint (struct breakpoint *bpkt); extern void set_ignore_count (int, int, int); -extern void set_default_breakpoint (int, struct program_space *, - CORE_ADDR, struct symtab *, int); - extern void breakpoint_init_inferior (enum inf_context); extern struct cleanup *make_cleanup_delete_breakpoint (struct breakpoint *); @@ -814,25 +1149,90 @@ extern void delete_breakpoint (struct breakpoint *); extern void breakpoint_auto_delete (bpstat); +typedef void (*walk_bp_location_callback) (struct bp_location *, void *); + +extern void iterate_over_bp_locations (walk_bp_location_callback); + +/* Return the chain of command lines to execute when this breakpoint + is hit. */ +extern struct command_line *breakpoint_commands (struct breakpoint *b); + +/* Return a string image of DISP. The string is static, and thus should + NOT be deallocated after use. */ +const char *bpdisp_text (enum bpdisp disp); + extern void break_command (char *, int); extern void hbreak_command_wrapper (char *, int); extern void thbreak_command_wrapper (char *, int); extern void rbreak_command_wrapper (char *, int); -extern void watch_command_wrapper (char *, int); -extern void awatch_command_wrapper (char *, int); -extern void rwatch_command_wrapper (char *, int); +extern void watch_command_wrapper (char *, int, int); +extern void awatch_command_wrapper (char *, int, int); +extern void rwatch_command_wrapper (char *, int, int); extern void tbreak_command (char *, int); +extern struct breakpoint_ops bkpt_breakpoint_ops; + +extern void initialize_breakpoint_ops (void); + +/* Arguments to pass as context to some catch command handlers. */ +#define CATCH_PERMANENT ((void *) (uintptr_t) 0) +#define CATCH_TEMPORARY ((void *) (uintptr_t) 1) + +/* Like add_cmd, but add the command to both the "catch" and "tcatch" + lists, and pass some additional user data to the command + function. */ + +extern void + add_catch_command (char *name, char *docstring, + void (*sfunc) (char *args, int from_tty, + struct cmd_list_element *command), + char **(*completer) (struct cmd_list_element *cmd, + char *text, char *word), + void *user_data_catch, + void *user_data_tcatch); + +/* Initialize a breakpoint struct for Ada exception catchpoints. */ + +extern void + init_ada_exception_breakpoint (struct breakpoint *b, + struct gdbarch *gdbarch, + struct symtab_and_line sal, + char *addr_string, + const struct breakpoint_ops *ops, + int tempflag, + int from_tty); + +/* Add breakpoint B on the breakpoint list, and notify the user, the + target and breakpoint_created observers of its existence. If + INTERNAL is non-zero, the breakpoint number will be allocated from + the internal breakpoint count. If UPDATE_GLL is non-zero, + update_global_location_list will be called. */ + +extern void install_breakpoint (int internal, struct breakpoint *b, + int update_gll); + +/* Flags that can be passed down to create_breakpoint, etc., to affect + breakpoint creation in several ways. */ + +enum breakpoint_create_flags + { + /* We're adding a breakpoint to our tables that is already + inserted in the target. */ + CREATE_BREAKPOINT_FLAGS_INSERTED = 1 << 0 + }; + extern int create_breakpoint (struct gdbarch *gdbarch, char *arg, char *cond_string, int thread, + char *extra_string, int parse_condition_and_thread, - int tempflag, int hardwareflag, int traceflag, + int tempflag, enum bptype wanted_type, int ignore_count, enum auto_boolean pending_break_support, - struct breakpoint_ops *ops, + const struct breakpoint_ops *ops, int from_tty, - int enabled); + int enabled, + int internal, unsigned flags); extern void insert_breakpoints (void); @@ -842,9 +1242,9 @@ extern int remove_breakpoints_pid (int pid); /* This function can be used to physically insert eventpoints from the specified traced inferior process, without modifying the breakpoint - package's state. This can be useful for those targets which support - following the processes of a fork() or vfork() system call, when both - of the resulting two processes are to be followed. */ + package's state. This can be useful for those targets which + support following the processes of a fork() or vfork() system call, + when both of the resulting two processes are to be followed. */ extern int reattach_breakpoints (int); /* This function can be used to update the breakpoint package's state @@ -861,7 +1261,7 @@ extern int reattach_breakpoints (int); - A step-resume breakpoint, if any, is explicitly removed from the breakpoint list. - All eventpoints without a symbolic address are removed from the - breakpoint list. */ + breakpoint list. */ extern void update_breakpoints_after_exec (void); /* This function can be used to physically remove hardware breakpoints @@ -880,9 +1280,13 @@ extern int detach_breakpoints (int); this PSPACE anymore. */ extern void breakpoint_program_space_exit (struct program_space *pspace); -extern void set_longjmp_breakpoint (int thread); +extern void set_longjmp_breakpoint (struct thread_info *tp, + struct frame_id frame); extern void delete_longjmp_breakpoint (int thread); +/* Mark all longjmp breakpoints from THREAD for later deletion. */ +extern void delete_longjmp_breakpoint_at_next_stop (int thread); + extern void enable_overlay_breakpoints (void); extern void disable_overlay_breakpoints (void); @@ -891,7 +1295,7 @@ extern void delete_std_terminate_breakpoint (void); /* These functions respectively disable or reenable all currently enabled watchpoints. When disabled, the watchpoints are marked - call_disabled. When reenabled, they are marked enabled. + call_disabled. When re-enabled, they are marked enabled. The intended client of these functions is call_function_by_hand. @@ -905,7 +1309,7 @@ extern void delete_std_terminate_breakpoint (void); and that can cause execution control to become very confused. Note that if a user sets breakpoints in an interactively called - function, the call_disabled watchpoints will have been reenabled + function, the call_disabled watchpoints will have been re-enabled when the first such breakpoint is reached. However, on targets that are unable to unwind through the call dummy frame, watches of stack-based storage may then be deleted, because gdb will @@ -928,20 +1332,17 @@ extern void disable_breakpoints_before_startup (void); extern void enable_breakpoints_after_startup (void); /* For script interpreters that need to define breakpoint commands - after they've already read the commands into a struct command_line. */ + after they've already read the commands into a struct + command_line. */ extern enum command_control_type commands_from_control_command (char *arg, struct command_line *cmd); extern void clear_breakpoint_hit_counts (void); -extern int get_number (char **); - -extern int get_number_or_range (char **); - extern struct breakpoint *get_breakpoint (int num); -/* The following are for displays, which aren't really breakpoints, but - here is as good a place as any for them. */ +/* The following are for displays, which aren't really breakpoints, + but here is as good a place as any for them. */ extern void disable_current_display (void); @@ -958,6 +1359,12 @@ extern void enable_breakpoint (struct breakpoint *); extern void breakpoint_set_commands (struct breakpoint *b, struct command_line *commands); +extern void breakpoint_set_silent (struct breakpoint *b, int silent); + +extern void breakpoint_set_thread (struct breakpoint *b, int thread); + +extern void breakpoint_set_task (struct breakpoint *b, int task); + /* Clear the "inserted" flag in all breakpoints. */ extern void mark_breakpoints_out (void); @@ -972,44 +1379,53 @@ extern struct breakpoint *create_solib_event_breakpoint (struct gdbarch *, extern struct breakpoint *create_thread_event_breakpoint (struct gdbarch *, CORE_ADDR); +extern void remove_jit_event_breakpoints (void); + extern void remove_solib_event_breakpoints (void); extern void remove_thread_event_breakpoints (void); extern void disable_breakpoints_in_shlibs (void); -/* This function returns TRUE if ep is a catchpoint. */ -extern int ep_is_catchpoint (struct breakpoint *); +/* This function returns TRUE if ep is a catchpoint. */ +extern int is_catchpoint (struct breakpoint *); /* Enable breakpoints and delete when hit. Called with ARG == NULL - deletes all breakpoints. */ + deletes all breakpoints. */ extern void delete_command (char *arg, int from_tty); -/* Pull all H/W watchpoints from the target. Return non-zero if the - remove fails. */ -extern int remove_hw_watchpoints (void); - -/* Manage a software single step breakpoint (or two). Insert may be called - twice before remove is called. */ +/* Manage a software single step breakpoint (or two). Insert may be + called twice before remove is called. */ extern void insert_single_step_breakpoint (struct gdbarch *, - struct address_space *, CORE_ADDR); + struct address_space *, + CORE_ADDR); +extern int single_step_breakpoints_inserted (void); extern void remove_single_step_breakpoints (void); +extern void cancel_single_step_breakpoints (void); /* Manage manual breakpoints, separate from the normal chain of breakpoints. These functions are used in murky target-specific ways. Please do not add more uses! */ extern void *deprecated_insert_raw_breakpoint (struct gdbarch *, - struct address_space *, CORE_ADDR); + struct address_space *, + CORE_ADDR); extern int deprecated_remove_raw_breakpoint (struct gdbarch *, void *); /* Check if any hardware watchpoints have triggered, according to the target. */ int watchpoints_triggered (struct target_waitstatus *); -/* Update BUF, which is LEN bytes read from the target address MEMADDR, - by replacing any memory breakpoints with their shadowed contents. */ -void breakpoint_restore_shadows (gdb_byte *buf, ULONGEST memaddr, - LONGEST len); +/* Helper for transparent breakpoint hiding for memory read and write + routines. + + Update one of READBUF or WRITEBUF with either the shadows + (READBUF), or the breakpoint instructions (WRITEBUF) of inserted + breakpoints at the memory range defined by MEMADDR and extending + for LEN bytes. If writing, then WRITEBUF is a copy of WRITEBUF_ORG + on entry.*/ +extern void breakpoint_xfer_memory (gdb_byte *readbuf, gdb_byte *writebuf, + const gdb_byte *writebuf_org, + ULONGEST memaddr, LONGEST len); extern int breakpoints_always_inserted_mode (void); @@ -1018,6 +1434,10 @@ extern int breakpoints_always_inserted_mode (void); in our opinion won't ever trigger. */ extern void breakpoint_retire_moribund (void); +/* Set break condition of breakpoint B to EXP. */ +extern void set_breakpoint_condition (struct breakpoint *b, char *exp, + int from_tty); + /* Checks if we are catching syscalls or not. Returns 0 if not, greater than 0 if we are. */ extern int catch_syscall_enabled (void); @@ -1027,23 +1447,27 @@ extern int catch_syscall_enabled (void); Returns 0 if not, greater than 0 if we are. */ extern int catching_syscall_number (int syscall_number); -/* Tell a breakpoint to be quiet. */ -extern void make_breakpoint_silent (struct breakpoint *); - /* Return a tracepoint with the given number if found. */ -extern struct breakpoint *get_tracepoint (int num); +extern struct tracepoint *get_tracepoint (int num); -extern struct breakpoint *get_tracepoint_by_number_on_target (int num); +extern struct tracepoint *get_tracepoint_by_number_on_target (int num); /* Find a tracepoint by parsing a number in the supplied string. */ -extern struct breakpoint *get_tracepoint_by_number (char **arg, int multi_p, - int optional_p); +extern struct tracepoint * + get_tracepoint_by_number (char **arg, + struct get_number_or_range_state *state, + int optional_p); /* Return a vector of all tracepoints currently defined. The vector is newly allocated; the caller should free when done with it. */ extern VEC(breakpoint_p) *all_tracepoints (void); -extern int breakpoint_is_tracepoint (const struct breakpoint *b); +extern int is_tracepoint (const struct breakpoint *b); + +/* Return a vector of all static tracepoints defined at ADDR. The + vector is newly allocated; the caller should free when done with + it. */ +extern VEC(breakpoint_p) *static_tracepoints_here (CORE_ADDR addr); /* Function that can be passed to read_command_line to validate that each command is suitable for tracepoint command list. */ @@ -1054,4 +1478,29 @@ extern void check_tracepoint_command (char *line, void *closure); extern void start_rbreak_breakpoints (void); extern void end_rbreak_breakpoints (void); +/* Breakpoint iterator function. + + Calls a callback function once for each breakpoint, so long as the + callback function returns false. If the callback function returns + true, the iteration will end and the current breakpoint will be + returned. This can be useful for implementing a search for a + breakpoint with arbitrary attributes, or for applying an operation + to every breakpoint. */ +extern struct breakpoint *iterate_over_breakpoints (int (*) (struct breakpoint *, + void *), void *); + +/* Nonzero if the specified PC cannot be a location where functions + have been inlined. */ + +extern int pc_at_non_inline_function (struct address_space *aspace, + CORE_ADDR pc, + const struct target_waitstatus *ws); + +extern int user_breakpoint_p (struct breakpoint *); + +/* Attempt to determine architecture of location identified by SAL. */ +extern struct gdbarch *get_sal_arch (struct symtab_and_line sal); + +extern void handle_solib_event (void); + #endif /* !defined (BREAKPOINT_H) */