[src/trunk]: src/gnu/dist/gdb6/gdb replace "(CORE_ADDR) (uintptr_t) NULL" by ...

[martin <martin%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/21e75735f97f
branches:  trunk
changeset: 767217:21e75735f97f
user:      martin <martin%NetBSD.org@localhost>
date:      Mon Jul 11 18:47:01 2011 +0000

description:
replace "(CORE_ADDR) (uintptr_t) NULL" by a simple "0" - avoids the dance
with HAVE_STDINT_H and fixes the tool build for me.
Idea from dsl, OK: mrg.

diffstat:

 gnu/dist/gdb6/gdb/breakpoint.c |  4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diffs (21 lines):

diff -r 5efe16d22958 -r 21e75735f97f gnu/dist/gdb6/gdb/breakpoint.c
--- a/gnu/dist/gdb6/gdb/breakpoint.c    Mon Jul 11 18:33:48 2011 +0000
+++ b/gnu/dist/gdb6/gdb/breakpoint.c    Mon Jul 11 18:47:01 2011 +0000
@@ -1327,7 +1327,7 @@
        (b->type == bp_catch_vfork) ||
        (b->type == bp_catch_fork))
       {
-       b->loc->address = (CORE_ADDR) (uintptr_t) NULL;
+       b->loc->address = 0;
        continue;
       }
 
@@ -1380,7 +1380,7 @@
        unnecessary.  A call to breakpoint_re_set_one always recomputes
        the breakpoint's address from scratch, or deletes it if it can't.
        So I think this assignment could be deleted without effect.  */
-    b->loc->address = (CORE_ADDR) (uintptr_t) NULL;
+    b->loc->address = 0;
   }
   /* FIXME what about longjmp breakpoints?  Re-create them here?  */
   create_overlay_event_breakpoint ("_ovly_debug_event");