From 6798554723617c1f63f3359e89aa96df72f9daf3 Mon Sep 17 00:00:00 2001 From: Thiemo Seufer Date: Tue, 8 Aug 2006 16:05:13 +0000 Subject: [PATCH] * breakpoint.c (update_breakpoints_after_exec): Fix type mismatch. --- gdb/ChangeLog | 4 ++++ gdb/breakpoint.c | 4 ++-- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 4669e8aee4d..5b829c2d95c 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,7 @@ +2006-08-08 Thiemo Seufer + + * breakpoint.c (update_breakpoints_after_exec): Fix type mismatch. + 2006-08-08 Vladimir Prus * symfile.c (download_write_size): Remove. diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c index 98db1401589..dcf33e33104 100644 --- a/gdb/breakpoint.c +++ b/gdb/breakpoint.c @@ -1327,7 +1327,7 @@ update_breakpoints_after_exec (void) (b->type == bp_catch_vfork) || (b->type == bp_catch_fork)) { - b->loc->address = (CORE_ADDR) NULL; + b->loc->address = (CORE_ADDR) 0; continue; } @@ -1380,7 +1380,7 @@ update_breakpoints_after_exec (void) 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) NULL; + b->loc->address = (CORE_ADDR) 0; } /* FIXME what about longjmp breakpoints? Re-create them here? */ create_overlay_event_breakpoint ("_ovly_debug_event"); -- 2.30.2