Imagelibrary/binutils-gdb
1
0
Fork 1
mirror of https://github.com/bminor/binutils-gdb.git synced 2025-12-28 10:00:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

2003-10-06 Andrew Cagney <cagney@redhat.com>

Browse Source 
* 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.
This commit is contained in:
Andrew Cagney
2003-10-06 19:27:13 +00:00
parent 28a86f5cc0
commit 41989fcd80
12 changed files with 14 additions and 1332 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
gdb/breakpoint.c
View File

@@ -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. */