diff options
| author | Andrew Cagney <cagney@redhat.com> | 2003-10-06 19:27:13 +0000 |
|---|---|---|
| committer | Andrew Cagney <cagney@redhat.com> | 2003-10-06 19:27:13 +0000 |
| commit | 408acf78bae0d7d1d5fc12ce7474ba9c6dd9a5b1 (patch) | |
| tree | ef424375fa6f20910fb969d7432730ceaa200047 /gdb/breakpoint.c | |
| parent | 5e42fb544abbf809b80aaa0d78c5a3eedb82b69d (diff) | |
| download | gdb-408acf78bae0d7d1d5fc12ce7474ba9c6dd9a5b1.tar.gz | |
2003-10-06 Andrew Cagney <cagney@redhat.com>
* breakpoint.c, breakpoint.h: Remove obsolete code and comments.
* buildsym.c, dbxread.c, gdbtypes.c, mdebugread.c: Ditto.
* monitor.c, sparc-tdep.c, stabsread.c: Ditto.
* stabsread.h, xcoffread.c: Ditto.
Diffstat (limited to 'gdb/breakpoint.c')
| -rw-r--r-- | gdb/breakpoint.c | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c index fa07e19392e..4b5b76ae358 100644 --- a/gdb/breakpoint.c +++ b/gdb/breakpoint.c @@ -1245,11 +1245,11 @@ update_breakpoints_after_exec (void) automagically. Certainly on HP-UX that's true. Jim Blandy <jimb@redhat.com>: Actually, zero is a perfectly - valid code address on some platforms (like the OBSOLETE mn10200 - and mn10300 simulators). We shouldn't assign any special - interpretation to a breakpoint with a zero address. And in - fact, GDB doesn't --- I can't see what that comment above is - talking about. As far as I can tell, setting the address of a + valid code address on some platforms (like the mn10300 + simulators). We shouldn't assign any special interpretation to + a breakpoint with a zero address. And in fact, GDB doesn't --- + I can't see what that comment above is talking about. As far + as I can tell, setting the address of a bp_catch_exec/bp_catch_vfork/bp_catch_fork breakpoint to zero is meaningless, since those are implemented with HP-UX kernel hackery, not by storing breakpoint instructions somewhere. */ |