From: "Uday Karan" <uday.karan@gmail.com>
To: "krishna.vamsi@wipro.com" <krishna.vamsi@wipro.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Startup function before main.
Date: Mon, 27 Mar 2006 17:31:36 +0530 [thread overview]
Message-ID: <4f2e7cd30603270401i51a6c167ncc3d74385b498a7c@mail.gmail.com> (raw)
In-Reply-To: <DC91351678E31E4FB24B551221F507EC028D5063@blr-itp-msg.wipro.com>
I really don't understand what is the need to have a
initialization/start up routine before main(). Main is just like any
other function except that it works as a default entry point to which
the glibc start up code makes a call to.
You can have a function main() as your start up routine that calls
your application's main functions app_main() or something similar.
You can do all your start up code in main itself and then call
app_main().
Simulating what you are trying to achieve here should not be very
difficult. You can tweak your environment and stuff in main().
On 3/27/06, krishna.vamsi@wipro.com <krishna.vamsi@wipro.com> wrote:
> Hi List,
>
> Before Executing the main function, a startup routine will be executed
> which will set up the initial environment for the process.
>
> This Startup routine will be supplied by the kernel and linked by the
> Linker. My question is : Can we add one more startup routine before
> executing the main program, if yes how??
>
>
> -Vamsi
> -
> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2006-03-27 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 11:07 Startup function before main krishna.vamsi
2006-03-27 11:48 ` Steve Graegert
2006-03-27 12:01 ` Uday Karan [this message]
2006-03-27 12:20 ` Steve Graegert
2006-03-27 17:48 ` Glynn Clements
-- strict thread matches above, loose matches on Subject: below --
2006-03-27 12:22 krishna.vamsi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f2e7cd30603270401i51a6c167ncc3d74385b498a7c@mail.gmail.com \
--to=uday.karan@gmail.com \
--cc=krishna.vamsi@wipro.com \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).