From 9efd18d33815d59900becfac7820902e15b6126e Mon Sep 17 00:00:00 2001
From: Eric Andersen <andersen@codepoet.org>
Date: Fri, 30 Jul 2004 20:06:01 +0000
Subject: s/___brk_addr/__curbrk/g Some utilities, such as valgrind, have a
 legitimate reason to know the address of the current brk.  Since we know such
 utils will peek under our skirt, we might as well give them what they expect
 and not use a gratuitously different symbol name.  -Erik

---
 libc/sysdeps/linux/mips/brk.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'libc/sysdeps/linux/mips/brk.c')

diff --git a/libc/sysdeps/linux/mips/brk.c b/libc/sysdeps/linux/mips/brk.c
index 82e44e461..c33111ed7 100644
--- a/libc/sysdeps/linux/mips/brk.c
+++ b/libc/sysdeps/linux/mips/brk.c
@@ -21,7 +21,7 @@
 #include <unistd.h>
 #include <sys/syscall.h>
 
-void *___brk_addr = 0;
+void *__curbrk = 0;
 
 int brk (void *addr)
 {
@@ -37,7 +37,7 @@ int brk (void *addr)
 	 : "$4", "$7");
     newbrk = (void *) res;
   }
-  ___brk_addr = newbrk;
+  __curbrk = newbrk;
 
   if (newbrk < addr)
     {
-- 
cgit v1.2.3