Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Fix build failure for MIPS gdb
Date: Tue, 08 Aug 2006 10:45:00 -0000	[thread overview]
Message-ID: <20060808104421.GD29989@networkno.de> (raw)

Hello All,

the appended patch fixes a type mismatch warning which is handled as
error (when using a recent gcc).


Thiemo


2006-08-08  Thiemo Seufer  <ths@mips.com>

	* breakpoint.c (update_breakpoints_after_exec): Fix type mismatch.


Index: breakpoint.c
===================================================================
RCS file: /cvs/src/src/gdb/breakpoint.c,v
retrieving revision 1.227
diff -u -p -r1.227 breakpoint.c
--- breakpoint.c	2 Jun 2006 03:43:18 -0000	1.227
+++ breakpoint.c	8 Aug 2006 10:16:54 -0000
@@ -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");


             reply	other threads:[~2006-08-08 10:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08 10:45 Thiemo Seufer [this message]
2006-08-08 13:08 ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060808104421.GD29989@networkno.de \
    --to=ths@networkno.de \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox