Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Replace complain() with complaint()
Date: Fri, 13 Dec 2002 13:18:00 -0000	[thread overview]
Message-ID: <1021213211537.ZM13136@localhost.localdomain> (raw)
In-Reply-To: Kevin Buettner <kevinb@redhat.com> "Re: [RFC] Replace complain() with complaint()" (Dec 13,  1:38pm)

On Dec 13,  1:38pm, Kevin Buettner wrote:

> On Dec 13,  3:21pm, Andrew Cagney wrote:
> 
> > > -	  complain (&anon_block_end_complaint, BLOCK_END (block), BLOCK_START (block));
> > > +	  complaint (&symfile_complaints,
> > > +		     "block end address 0x%lx less than block start address 0x%lx (patched it)",
> > > +		     BLOCK_END (block), BLOCK_START (block));
> > 
> > Hmm, I don't think that is right.  It should have attacted a -Wformat 
> > warning as block start/end are core-addrs.  From memory though, a native 
> > i386 build has CORE_ADDR as a long which might explain why you don't see 
> > the warning.
[...]
> I'll try a cross build for a 64-bit target...

Okay, now I see a -Wformat warning.  Fortunately, buildsym.c was the only
file affected.  Below are the diffs that I propose using for that file.
(These take the place of the buildsym.c diffs that I previously posted.)
The ChangeLog entries remain the same.

Note the use of paddr_nz() to convert the CORE_ADDR to a string.  According
to defs.h, this most closely corresponds to the %lx format.  Also, the
paddr() family of functions have an advantage over local_hex_string_custom()
(and the like) in that it's safe to use several of these calls together
without having to worry about the internal storage being overwritten.

Index: buildsym.c
===================================================================
RCS file: /cvs/src/src/gdb/buildsym.c,v
retrieving revision 1.23
diff -u -p -r1.23 buildsym.c
--- buildsym.c	18 Nov 2002 20:57:55 -0000	1.23
+++ buildsym.c	13 Dec 2002 21:07:14 -0000
@@ -73,23 +73,6 @@ static int compare_line_numbers (const v
 #define	INITIAL_LINE_VECTOR_LENGTH	1000
 \f
 
-/* Complaints about the symbols we have encountered.  */
-
-struct deprecated_complaint block_end_complaint =
-{"block end address less than block start address in %s (patched it)", 0, 0};
-
-struct deprecated_complaint anon_block_end_complaint =
-{"block end address 0x%lx less than block start address 0x%lx (patched it)", 0, 0};
-
-struct deprecated_complaint innerblock_complaint =
-{"inner block not inside outer block in %s", 0, 0};
-
-struct deprecated_complaint innerblock_anon_complaint =
-{"inner block (0x%lx-0x%lx) not inside outer block (0x%lx-0x%lx)", 0, 0};
-
-struct deprecated_complaint blockvector_complaint =
-{"block at %s out of order", 0, 0};
-\f
 /* maintain the lists of symbols and blocks */
 
 /* Add a pending list to free_pendings. */
@@ -408,11 +391,15 @@ finish_block (struct symbol *symbol, str
     {
       if (symbol)
 	{
-	  complain (&block_end_complaint, SYMBOL_SOURCE_NAME (symbol));
+	  complaint (&symfile_complaints,
+		     "block end address less than block start address in %s (patched it)",
+		     SYMBOL_SOURCE_NAME (symbol));
 	}
       else
 	{
-	  complain (&anon_block_end_complaint, BLOCK_END (block), BLOCK_START (block));
+	  complaint (&symfile_complaints,
+		     "block end address 0x%s less than block start address 0x%s (patched it)",
+		     paddr_nz (BLOCK_END (block)), paddr_nz (BLOCK_START (block)));
 	}
       /* Better than nothing */
       BLOCK_END (block) = BLOCK_START (block);
@@ -438,14 +425,18 @@ finish_block (struct symbol *symbol, str
 	    {
 	      if (symbol)
 		{
-		  complain (&innerblock_complaint,
-			    SYMBOL_SOURCE_NAME (symbol));
+		  complaint (&symfile_complaints,
+			     "inner block not inside outer block in %s",
+			     SYMBOL_SOURCE_NAME (symbol));
 		}
 	      else
 		{
-		  complain (&innerblock_anon_complaint, BLOCK_START (pblock->block),
-			    BLOCK_END (pblock->block), BLOCK_START (block),
-			    BLOCK_END (block));
+		  complaint (&symfile_complaints,
+			     "inner block (0x%s-0x%s) not inside outer block (0x%s-0x%s)",
+			     paddr_nz (BLOCK_START (pblock->block)),
+			     paddr_nz (BLOCK_END (pblock->block)),
+			     paddr_nz (BLOCK_START (block)),
+			     paddr_nz (BLOCK_END (block)));
 		}
 	      if (BLOCK_START (pblock->block) < BLOCK_START (block))
 		BLOCK_START (pblock->block) = BLOCK_START (block);
@@ -550,8 +541,8 @@ make_blockvector (struct objfile *objfil
 	      CORE_ADDR start
 		= BLOCK_START (BLOCKVECTOR_BLOCK (blockvector, i));
 
-	      complain (&blockvector_complaint,
-			local_hex_string ((LONGEST) start));
+	      complaint (&symfile_complaints, "block at %s out of order",
+			 local_hex_string ((LONGEST) start));
 	    }
 	}
     }
@@ -870,9 +861,8 @@ end_symtab (CORE_ADDR end_addr, struct o
 	     same.  FIXME: Find out why it is happening.  This is not
 	     believed to happen in most cases (even for coffread.c);
 	     it used to be an abort().  */
-	  static struct deprecated_complaint msg =
-	  {"Context stack not empty in end_symtab", 0, 0};
-	  complain (&msg);
+	  complaint (&symfile_complaints,
+	             "Context stack not empty in end_symtab");
 	  context_stack_depth = 0;
 	}
     }


  reply	other threads:[~2002-12-13 21:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11 21:18 Kevin Buettner
2002-12-13 12:34 ` Andrew Cagney
2002-12-13 12:44   ` Kevin Buettner
2002-12-13 13:18     ` Kevin Buettner [this message]
2002-12-13 13:59       ` Andrew Cagney
2002-12-13 15:20         ` Kevin Buettner
2002-12-16 17:23 ` Kevin Buettner
2002-12-17  4:28   ` Andrew Cagney

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=1021213211537.ZM13136@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=ac131313@redhat.com \
    --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