The generated binary code has different main?

From: Minchu Mo (morris_minchu@iwon.com)
Date: 09/04/02 

Date: 4 Sep 2002 21:48:38 -0000
From: Minchu Mo <morris_minchu@iwon.com>
To: vuln-dev@securityfocus.com
('binary' encoding is not supported, stored as-is)

I used cc compiler to compile a simple c code under solaris /sparc. The c
code has main(int argc, char* argv[]) function as entry point as everybody
knows.

But when I run the generated code under adb, I found the main function
under adb look like this:

main(2,ffbefd0c,ffbefd18,20800,0,0)

I know that:
2 is the number of arguments,
ffbefd0c is *argv
ffbefd18 is *envp,
but what are 20800 and 0, 0 for?

Anybody knows? Thanks

Relevant Pages

  • RE: The generated binary code has different main?
    ... I used cc compiler to compile a simple c code under solaris /sparc. ... char* argv[]) function as entry point as ... But when I run the generated code under adb, ... ffbefd0c is *argv ...
    (Vuln-Dev)
  • Re: gcc 4.2 profiling breaks argv
    ... Programs segfault when attempting to access argv from main when compiled under gcc 4.2.0 with the -pg profiling option. ... Configured with: FreeBSD/i386 system compiler ...
    (freebsd-current)
  • gcc 4.2 profiling breaks argv
    ... Programs segfault when attempting to access argv from main when compiled under gcc 4.2.0 with the -pg profiling option. ... Configured with: FreeBSD/i386 system compiler ...
    (freebsd-current)
  • Re: gcc 4.2 profiling breaks argv
    ... Programs segfault when attempting to access argv from main when compiled ... under gcc 4.2.0 with the -pg profiling option. ... Configured with: FreeBSD/i386 system compiler ...
    (freebsd-current)
  • Re: gcc 4.2 profiling breaks argv
    ... Programs segfault when attempting to access argv from main when compiled under gcc 4.2.0 with the -pg profiling option. ... Configured with: FreeBSD/amd64 system compiler ...
    (freebsd-current)