Lines Matching defs:is

7    This file is part of GDB.
9 This program is free software; you can redistribute it and/or modify
14 This program is distributed in the hope that it will be useful,
212 if such is available. */
273 reinitialized -- e.g. when program is re-run */
280 This function must be used only when SOLIB_HAVE_LOAD_EVENT is TRUE,
285 invalid as soon as the inferior is continued. Clients should make
297 This function must be used only when SOLIB_HAVE_UNLOAD_EVENT is
302 invalid as soon as the inferior is continued. Clients should make
310 /* This function is called by the "catch load" command. It allows the
312 library file (or any library file, if filename is NULL) is loaded. */
319 /* This function is called by the "catch unload" command. It allows
321 library file (or any library file, if filename is NULL) is
329 /* Return whether a breakpoint is an active enabled breakpoint. */
359 if default_breakpoint_valid is zero, the other three are
360 not valid, and "break" with no arg is an error.
370 /* *PP is a string denoting a breakpoint. Get the number of the breakpoint.
377 TRAILER is a character which can be found after the number; most
378 commonly this is `-'. If you don't want a trailer, use \0. */
417 /* There is no number here. (e.g. "cond a == b"). */
455 * While processing a range, this fuction is called iteratively;
461 * is completed. The call that completes the range will advance
474 /* Default case: pp is pointing either to a solo number,
481 /* This is the start of a range (<number1> - <number2>).
513 is reached. */
566 /* I don't know if it matters whether this is the string the user
608 char *tmpbuf = xstrprintf ("Type commands for when breakpoint %d is hit, one per line.",
627 Returns zero if successful, errno value if not. EIO is used
667 /* The breakpoint is entirely before the chunk of memory we
671 /* The breakpoint is entirely after the chunk of memory we are
752 /* Insert a low-level "breakpoint" of some type. BPT is the breakpoint.
793 /* This breakpoint is in an overlay section.
797 /* Yes -- overlay event support is not active,
818 /* Yes. This overlay section is mapped into memory. */
896 must watch. As soon as a many-to-one mapping is available I'll
912 /* Determine if the watchpoint is within scope. */
999 printf_filtered ("in which its expression is valid.\n");
1092 /* insert_breakpoints is used when starting or continuing the program.
1093 remove_breakpoints is used when the program stops.
1237 shadow is NOT valid after an exec()! */
1282 on this target, we may not be able to stop when the vfork is
1283 seen, but only when the subsequent exec is seen. (And because
1288 target address field, if any, is sufficient to have it be reset
1291 Jim Blandy <jimb@redhat.com>: Actually, zero is a perfectly
1295 I can't see what that comment above is talking about. As far
1298 is meaningless, since those are implemented with HP-UX kernel
1308 /* bp_finish is a special case. The only way we ought to be able
1309 to see one of these when an exec() has happened, is if the user
1325 problem, what we'll do here is just uninsert the bp_finish, and
1328 (We know the bp_finish is "doomed" in the sense that it's
1331 address is probably bogus in the new a.out, unlike e.g., the
1353 for bp_catch_exec and friends, I'm pretty sure this is entirely
1392 remove_breakpoint (struct bp_location *b, insertion_state_t is)
1426 /* This breakpoint is in an overlay section.
1430 /* Yes -- overlay event support is not active, so we
1435 /* Ignore any failures: if the LMA is in ROM, we will
1465 b->inserted = (is == mark_inserted);
1474 b->inserted = (is == mark_inserted);
1508 if ((is == mark_uninserted) && (b->inserted))
1513 the next time the watchpoint is inserted. */
1545 b->inserted = (is == mark_inserted);
1556 b->inserted = (is == mark_inserted);
1568 b->inserted = (is == mark_inserted);
1614 /* If the call dummy breakpoint is at the entry point it will
1615 cause problems when the inferior is rerun, so we better
1688 && bpt->address == pc) /* bp is enabled and matches pc */
1705 /* breakpoint_inserted_here_p (PC) is just like breakpoint_here_p(),
1706 but it only returns true if there is actually a breakpoint inserted
1721 && bpt->address == pc) /* bp is inserted and matches pc */
1735 /* This function returns non-zero iff there is a software breakpoint
1752 && bpt->address == pc) /* bp is enabled and matches pc */
1766 /* Return nonzero if FRAME is a dummy frame. We can't use
1777 /* This function is used by two files: get_frame_type(), after first
1798 PC is valid for process/thread PTID. */
1868 Also free any storage that is part of a bpstat. */
1892 is part of the bpstat is copied as well. */
1914 /* This is the first thing in the chain. */
1944 It is an error to use this function if BPSTAT doesn't contain a
1972 at. *BSP upon return is a bpstat which points to the remaining
1973 breakpoints stopped at (but which is not guaranteed to be good for
2029 /* Avoid endless recursion if a `source' command is contained
2083 /* The inferior is proceeded by the command; bomb out now.
2085 But since execution has stopped again, there is a new bpstat
2092 /* This is the normal print function for a bpstat. In the future,
2096 Current scheme: When we stop, bpstat_print() is called. It loops
2406 /* Print a message indicating what happened. This is called from
2407 normal_stop(). The input to this routine is the head of the bpstat
2412 routine is one of:
2416 code to print the location. An example is
2419 PRINT_SRC_ONLY: Means we printed something, but there is no need
2421 An example is the catch/throw messages, which
2433 That probably could (should) be changed, provided care is taken
2449 /* Evaluate the expression EXP and return 1 if value is zero.
2450 This is used inside a catch_errors to evaluate the breakpoint condition.
2451 The argument is a "struct expression *" that has been cast to char * to
2473 /* If the condition is false, etc., don't do the commands. */
2509 /* There is no current frame at this moment. If we're going to have
2523 because the current PC is currently in an epilogue. Calling
2565 we reenter the block in which it is valid it contains
2580 which its expression is valid.\n");
2594 don't understand this stop. Result is a chain of bpstat's such that:
2596 if we don't understand the stop, the result is a null pointer.
2598 if we understand why we stopped, the result is not null.
2719 /* Actually this is superfluous, because by the time we
2774 /* Exact match not required. Within range is
2801 the value has changed. This is for targets
2828 /* This is a case where some watchpoint(s) triggered,
2839 /* By definition, an encountered breakpoint is a triggered
2966 /* This is just used to count how many enums there are. */
2970 /* Here is the table which drives this routine. So that we can
2986 abort() is not out of the question, but chances are GDB is just
2991 /* One interesting property of this table is that wp_silent is the same
2992 as bp_silent and wp_noisy is the same as bp_noisy. That is because
2994 (BPSTAT_WHAT_SINGLE type stuff) is handled in proceed() without
2998 Another possibly interesting property of this table is that
3000 you've decided that some action is appropriate, you'll never go
3001 back and decide something of a lower priority is better. The
3002 ordering is:
3016 What I think this means is that we don't need a damned table
3022 is messy anyway). */
3028 one of those and a step_resume_breakpoint is probably very rare (?). */
3132 /* It is for the wrong frame. */
3186 /* Make sure the action is stop (silent or noisy),
3388 /* Field 4, the address, is omitted (which makes the columns
3390 is relatively readable). */
3400 /* Field 4, the address, is omitted (which makes the columns
3402 is relatively readable). */
3421 /* Field 4, the address, is omitted (which makes the columns
3423 is relatively readable). */
3435 /* Field 4, the address, is omitted (which makes the columns
3437 is relatively readable). */
3450 /* Field 4, the address, is omitted (which makes the columns
3452 is relatively readable). */
3461 /* Field 4, the address, is omitted (which makes the columns
3463 is relatively readable). */
3581 /* Output the count also if it is zero, but only if this is
3641 /* Return non-zero if B is user settable (breakpoints, watchpoints,
3663 number BNUM. If BNUM is -1 print all user settable breakpoints.
3664 If ALLFLAG is non-zero, include non- user settable breakpoints. */
3728 allflag is set. */
3746 that a comparison of an unsigned with -1 is always false. */
3751 /* FIXME? Should this be moved up so that it is only called when
3830 /* Return true iff it is meaningful to use the address member of
3831 BPT. For some breakpoint types, the address member is irrelevant
3866 This is so that the bpt instruction is only inserted once.
3912 "allegedly permanent breakpoint is not "
3956 this function is simply the identity function. */
3977 is required. */
4050 /* set_raw_breakpoint() is a low level routine for allocating and
4054 initialized breakpoint is added to the breakpoint chain and
4055 is also returned as the value of this function.
4057 It is expected that the caller will complete the initialization of
4310 is now loaded. */
4409 is still not mapped in. */
4685 Restrict it to frame FRAME if FRAME is nonzero. */
4720 /* FIXME: This is misplaced; mention() is called by things (like hitting a
4860 The parameter PENDING_BP points to a pending breakpoint that is
4865 NOTE: If the function succeeds, the caller is expected to cleanup
4867 array contents). If the function fails (error() is called), the
4868 caller is expected to cleanups both the ADDR_STRING, COND_STRING,
4945 /* Parse ARG which is assumed to be a SAL specification possibly
4958 /* If no arg given, or if first arg is 'if ', use the default
4982 current_source_symtab (which is decode_line_1's default). This
5036 minimal symbol for the "foo", but it's address is invalid.
5038 when the inferior is run.)
5068 PENDING_BP is non-NULL when this function is being called to resolve
5108 /* If caller is interested in rc value from parse, set value. */
5122 /* If pending breakpoint support is turned off, throw error. */
5127 /* If pending breakpoint support is auto query and the user selects
5135 behavior is on and thus a pending breakpoint is defaulted
5171 Anything added to the cleanup chain beyond this point is assumed
5173 then the memory is not reclaimed. */
5331 /* Always have a addr_string array, even if it is empty. */
5346 Anything added to the cleanup chain beyond this point is assumed
5348 through then that memory is not cleaned up. */
5612 /* It really is worthwhile to have the section, so we'll just
5689 /* look for a ':'. If this is a line number specification, then
5690 say it is bad, otherwise, it should be an address or
5722 /* look for a ':'. If there is a '::' then get out, otherwise
5723 it is probably a line number. */
5874 /* If the expression is "local", then set up a "watchpoint scope"
5899 /* The scope breakpoint is related to the watchpoint. We
5937 The idea here is that evaluating an expression generates a series
5956 /* A lazy memory lvalue is one that GDB never needed to fetch;
6035 /* This function is called by fetch_inferior_event via the
6102 where we get a chance to do that is in fetch_inferior_event, so
6107 /* In this case the arg for the continuation is just the point
6109 cleanups, because all the continuation does is the cleanups in
6135 of if we are, but the target is still synchronous. */
6151 possible match is found, a pointer to the last character of
6152 the token is returned. Else, NULL is returned. */
6180 from the arg string. If one is not found, it returns NULL.
6210 string. If one is not found, it returns NULL.
6213 makes no attempt to verify that a file of that name exists, or is
6262 /* The allowed syntax is:
6295 /* The allowed syntax is:
6318 /* The allowed syntax is:
6324 The user is not allowed to specify the <filename> after an
6360 /* The allowed syntax is:
6366 The user is not allowed to specify the <filename> after an
6573 return 1; /*is valid */
6582 then attempt to interpret it as an exception name. (This latter is
6595 /* Now, this is not allowed */
6671 /* Now this is not allowed */
6741 behavior that from_tty is forced true if we delete more than
6772 /* Not if b is a watchpoint of any sort... */
6787 /* b is at the head of the list */
6834 This is called after any breakpoint is hit, or after errors. */
6870 One example of this happening is a watchpoint's scope bp. When the
6871 scope bp triggers, we notice that the watchpoint is out of scope, and
6872 delete it. We also delete its scope bp. But the scope bp is marked
6873 "auto-deleting", and is already on a bpstat. That bpstat is then
6933 /* If this breakpoint was inserted, and there is another breakpoint
6954 /* We should never reach this point if there is a permanent
6956 If there is a permanent breakpoint somewhere, it should
7134 ``And a hack it is, although Apple's Darwin version of GDB
7137 but it is easy to come up with a test case where the patch
7145 Fixing this is not trivial. Therefore, I'm not sure whether
7227 /* Now that this is re-enabled, check_duplicates
7243 functionname, but if the context is more local than that, the
7291 that requests them is unaffected by e.g., new libraries being
7309 /* This breakpoint is special, it's set up when the inferior
7313 /* Like bp_shlib_event, this breakpoint type is special.
7314 Once it is set up, we do not want to touch it. */
7318 over a dlopen call and SOLIB_ADD is resetting the breakpoints.
7369 - If the breakpoint is for all threads, leave it as-is.
7382 If from_tty is nonzero, it prints a message to that effect,
7400 printf_filtered ("Will stop next time breakpoint %d is reached.",
7442 error ("Second argument (specified ignore-count) is missing.");
7497 If from_tty is nonzero, it prints a message to that effect,
7581 is resolvable since shared libraries could have been loaded
7614 is valid is not currently in scope.\n", bpt->number);
7642 /* we can consider of type is bp_hardware_watchpoint, convert to
7775 before a breakpoint is set. */
7780 Usage is `ignore N COUNT'.");
7785 "Set commands to be executed when a breakpoint is hit.\n\
7787 With no argument, the targeted breakpoint is the last one set.\n\
7791 then no output is printed when it is hit, except what the commands print.");
7794 "Specify breakpoint number N to break only if COND is true.\n\
7795 Usage is `condition N COND', where N is an integer and COND is an\n\
7796 expression to be evaluated whenever breakpoint N is reached.");
7800 Like \"break\" except the breakpoint is only temporary,\n\
7813 Like \"hbreak\" except the breakpoint is only temporary,\n\
7821 This is used to cancel the effect of the \"disable\" command.\n\
7829 This is used to cancel the effect of the \"disable\" command.\n\
7837 This is used to cancel the effect of the \"disable\" command.\n\
7843 If a breakpoint is hit while enabled in this fashion, it becomes disabled.",
7848 If a breakpoint is hit while enabled in this fashion, it is deleted.",
7853 If a breakpoint is hit while enabled in this fashion, it is deleted.",
7858 If a breakpoint is hit while enabled in this fashion, it becomes disabled.",
7865 A disabled breakpoint is not forgotten, but has no effect until reenabled.",
7874 A disabled breakpoint is not forgotten, but has no effect until reenabled.");
7880 A disabled breakpoint is not forgotten, but has no effect until reenabled.\n\
7890 The \"unset\" command is also an alias for \"delete\".",
7909 If line number is specified, all breakpoints in that line are cleared.\n\
7910 If function is specified, breakpoints at beginning of function are cleared.\n\
7911 If an address is specified, breakpoints at that address are cleared.\n\n",
7913 is executing in.\n\
7920 If line number is specified, break at start of code for that line.\n\
7921 If function is specified, break at start of code for that function.\n\
7922 If an address is specified, break at that exact address.\n",
7924 This is useful for breaking on return to a stack frame.\n\
8046 after a fork or vfork is caught.\n\n\
8052 Like \"catch\" except the catchpoint is only temporary,\n\
8065 an expression is read.");
8071 an expression is either read or written.");
8082 such is available. (However, any hardware watchpoints that were\n\