|
From: <sv...@va...> - 2005-04-25 15:43:19
|
Author: sewardj
Date: 2005-04-25 16:42:57 +0100 (Mon, 25 Apr 2005)
New Revision: 3565
Modified:
trunk/coregrind/vg_malloc2.c
Log:
Use __FUNCTION__ correctly.
Modified: trunk/coregrind/vg_malloc2.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/coregrind/vg_malloc2.c 2005-04-25 11:11:44 UTC (rev 3564)
+++ trunk/coregrind/vg_malloc2.c 2005-04-25 15:42:57 UTC (rev 3565)
@@ -390,14 +390,16 @@
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)",=20
+ __PRETTY_FUNCTION__, (ULong)rz_szB);
VG_(exit)(1);
}
client_malloc_redzone_szB =3D rz_szB;
|