This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Calling exit in a Redboot standalone Arm program
- From: Mark Salter <msalter at redhat dot com>
- To: Pierre dot Habraken at imag dot fr
- Cc: jifl at eCosCentric dot com, ecos-discuss at sources dot redhat dot com
- Date: Thu, 1 May 2003 11:32:04 -0400 (EDT)
- Subject: Re: [ECOS] Calling exit in a Redboot standalone Arm program
- References: <3EA53C1E.231D1898@imag.fr> <20030422132718.70DE07885A@deneb.localdomain> <3EA5646A.5CF9F526@imag.fr> <3EA5B1B8.8020205@eCosCentric.com> <20030423020915.A942A7885A@deneb.localdomain> <3EA74B92.1050107@eCosCentric.com> <3EB13580.9E282799@imag.fr>
>>>>> Pierre Habraken writes:
> In accordance with Mark's previous warning I checked that this time
> quitting gdb makes RedBoot return to its main prompt.
> BTW, Mark, you expressed in an other message some doubts about the use
> of HAL_THREAD_* macros. What about the patch as it was proposed by
> Jonathan ?
I'm just concerned that the CYGACC_CALL_IF_MONITOR_RETURN call will
not work from an exception context on all architectures. It will
work for ARM, but I believe there are others where it won't work.
I'm thinking of architectures like sparc where there are explicit
instructions used to return from exceptions. Since, the call to
CYGACC_CALL_IF_MONITOR_RETURN from the exit code is in an exception
context, the HAL_THREAD_LOAD_CONTEXT macro used by return_to_redboot()
may not do the right thing.
--Mark
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss