Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [patch/5.2/commit] Zap __func__
Date: Mon, 15 Jul 2002 09:50:00 -0000	[thread overview]
Message-ID: <3D32FB89.8030403@ges.redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 117 bytes --]

Just FYI,

I've committed this to the 5.2 branch - zap more __func__s.  It's brutal 
but it works :-)

enjoy,
Andrew

[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1154 bytes --]

2002-07-15  Andrew Cagney  <ac131313@redhat.com>

	* dwarf2cfi.c: Replace __func__ with "?func?".

Index: dwarf2cfi.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2cfi.c,v
retrieving revision 1.1.2.5
diff -u -r1.1.2.5 dwarf2cfi.c
--- dwarf2cfi.c	3 Jul 2002 06:00:26 -0000	1.1.2.5
+++ dwarf2cfi.c	15 Jul 2002 16:40:58 -0000
@@ -860,7 +860,7 @@
     }
   else
     internal_error (__FILE__, __LINE__,
-		    "%s(): Internal error: fde->cie_ptr==NULL !", __func__);
+		    "%s(): Internal error: fde->cie_ptr==NULL !", "?func?");
 }
 
 static void
@@ -1361,7 +1361,7 @@
 	      orig_context->reg[fs->regs.reg[i].loc.reg].loc.addr;
 	  default:
 	    internal_error (__FILE__, __LINE__,
-			    "%s: unknown register rule", __func__);
+			    "%s: unknown register rule", "?func?");
 	  }
 	break;
       case REG_SAVED_EXP:
@@ -1379,7 +1379,7 @@
 	break;
       default:
 	internal_error (__FILE__, __LINE__,
-			"%s: unknown register rule", __func__);
+			"%s: unknown register rule", "?func?");
       }
   get_reg ((char *) &context->ra, context, fs->retaddr_column);
   unwind_tmp_obstack_free ();

             reply	other threads:[~2002-07-15 16:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-15  9:50 Andrew Cagney [this message]
2002-07-15 11:18 ` Daniel Jacobowitz
2002-07-15 13:09   ` Andrew Cagney
2002-07-15 13:42     ` Daniel Jacobowitz
2002-07-15 15:00       ` 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=3D32FB89.8030403@ges.redhat.com \
    --to=ac131313@ges.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