mcheck(a,b)



In Bash 3.0, there is a call to mcheck() with 2 arguments. The
prototype in mcheck.h has only 1 argument. The function definition in
glibc only has 1 argument. Does anyone know why the call from bash
gives a 2nd argument? Was there an expectation that mcheck would be
expanded to take a second argument?

.



Relevant Pages

  • Re: mcheck(a,b)
    ... glibc only has 1 argument. ... Does anyone know why the call from bash ... the interface changing in the next release of glibc) ...
    (comp.os.linux.development.apps)
  • Re: Bash bug
    ... David Empson wrote: ... {then it is treated by bash as a function definition. ... The first semicolon terminates that command ... and the closing brace terminates the function definition. ...
    (uk.comp.sys.mac)
  • Re: glibc glob_filename() recurse call stack overflow (Re[2]: Bash Blues)
    ... a bug in glibc. ... In the bash source file ... If it is a problem with glibc then other programs ...
    (Vuln-Dev)
  • Re: BASH vulnerability
    ... bash: warning: x: ignoring function definition attempt ... Bash is vulnerable! ... environment, so whenever a new instance starts it scans it's environment ... but due to a long-standing bug it will also execute as ...
    (comp.sys.mac.system)
  • Re: [opensuse] Remote exploit vulnerability in bash CVE-2014-6271
    ... bash: warning: x: ignoring function definition attempt ... error importing function definition for `x' ...
    (SuSE)