From 9efd18d33815d59900becfac7820902e15b6126e Mon Sep 17 00:00:00 2001 From: Eric Andersen 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/sh64/__init_brk.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'libc/sysdeps/linux/sh64/__init_brk.c') diff --git a/libc/sysdeps/linux/sh64/__init_brk.c b/libc/sysdeps/linux/sh64/__init_brk.c index 7f9cd3c31..c9a2a3ec5 100644 --- a/libc/sysdeps/linux/sh64/__init_brk.c +++ b/libc/sysdeps/linux/sh64/__init_brk.c @@ -4,7 +4,7 @@ #include #include -void * ___brk_addr = 0; +void * __curbrk = 0; #define __NR__brk __NR_brk _syscall1(void *, _brk, void *, ptr); @@ -12,10 +12,10 @@ _syscall1(void *, _brk, void *, ptr); int __init_brk (void) { - if (___brk_addr == 0) + if (__curbrk == 0) { - ___brk_addr = _brk(0); - if (___brk_addr == 0) + __curbrk = _brk(0); + if (__curbrk == 0) { __set_errno(ENOMEM); return -1; -- cgit v1.2.3