From: Julian Seward <jseward@acm.org>
Date: Mon, 25 Apr 2005 15:42:57 +0000 (+0000)
Subject: Use __FUNCTION__ correctly.
X-Git-Tag: svn/VALGRIND_3_0_0~753
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=894840bfcb69b2374f0e6eb69481861258d2dfb7;p=thirdparty%2Fvalgrind.git

Use __FUNCTION__ correctly.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3565
---

diff --git a/coregrind/vg_malloc2.c b/coregrind/vg_malloc2.c
index 00e0ee421d..e7aebdd2e7 100644
--- a/coregrind/vg_malloc2.c
+++ b/coregrind/vg_malloc2.c
@@ -390,14 +390,16 @@ void VG_(set_client_malloc_redzone_szB)(SizeT rz_szB)
    if (init_done) {
       VG_(printf)(
          "\nTool error:\n"
-         "  __FUNCTION__ cannot be called after the first allocation.\n");
+         "%s cannot be called after the first allocation.\n",
+         __PRETTY_FUNCTION__);
       VG_(exit)(1);
    }
    // This limit is no special figure, just something not too big
    if (rz_szB > 128) {
       VG_(printf)(
          "\nTool error:\n"
-         "  __FUNCTION__ passed a too-big value (%llu)", (ULong)rz_szB);
+         "  %s passed a too-big value (%llu)", 
+         __PRETTY_FUNCTION__, (ULong)rz_szB);
       VG_(exit)(1);
    }
    client_malloc_redzone_szB = rz_szB;