This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Newbie-Q: Clean exits from tests and examples
- From: Sergei Gavrikov <w3sg at SoftHome dot net>
- To: John Mills <john dot m dot mills at alum dot mit dot edu>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Wed, 16 May 2007 21:16:13 +0300
- Subject: Re: [ECOS] Newbie-Q: Clean exits from tests and examples
- References: <Pine.LNX.4.44.0705160934220.2647-100000@otter.localdomain>
On Wed, May 16, 2007 at 09:58:53AM -0500, John Mills wrote:
> Hello -
>
> I'm getting started with the eCos-2.0 'synthetic' target and have a couple
> of beginner's questions.
>
> I used the command line setup:
>
> $ ecosconfig new linux default
>
> [edited 'ecos.ecc' tools prefix to match my installation]
>
> $ ecosconfig tree
> $ make
> $ make tests
>
> All this went fine.
>
> I copied the 'ecos-2.0/examples' directory into my scratch directory
> and can built the executables, which also went fine:
>
> $ cd examples
> $ make INSTALL_DIR=<my_install>
>
> The 'install/.../tests' like 'wallclock' run and exit fine. The 'examples'
> run fine,
> but don't exit (i.e., 'hello' prints its output then sits until I kill it
> with '^C').
>
> $ ~/sandbox/ecos/examples> ./hello
> Hello, eCos world!
> [and here we stay until I issue a '^C']
>
> Question: How should 'examples/hello.c' be structured to run and exit,
> returning cleanly to the parent Linux shell, or how should I invoke it?
>
Answer: main(){printf("hello, world!\n");cyg_hal_sys_exit(0);}
That's normal. The _tests_ for the synthetic target usually is finished
by the CYGHWR_TEST_PROGRAM_EXIT (include/cyg/hal/hal_intr.h). So, there
is the cyg_hal_sys_exit(0) in those wallclock* tests.
And you can see that examples/hello.c exits from main with return 0.
That's UNIX way. But eCos != UNIX. Where has to return the application?
You can easy see the difference using GDB, set a breakpoint either to
the 'cyg_test_exit' call (for the tests) or to the 'exit' call (for the
POSIX sources). And more, try to run the synthetic executables from
shell as 'appname --io'.
Sergei
> Thanks.
>
> - John Mills
> john.m.mills@alum.mit.edu
>
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss