This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Problems with running applications
- To: Peter Blair <peterb at turnpikeglobal dot com>
- Subject: Re: [ECOS] Problems with running applications
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Tue, 21 Aug 2001 21:44:25 +0100
- Cc: ecos-discuss at sources dot redhat dot com
- Organization: Red Hat UK Ltd.
- References: <8669764C0A96B640AE8A6F5BB7C259D955D6@turnpdcf1.home.turnpikeglobal.com>
Peter Blair wrote:
>
> I did load the application via GDB/Insight, just as you described in
> your prior message.
Not in the command-line GDB trace you gave.
> As described in my previous message all transfers using GDB/Insight
> occur without problem-- the problem arrises when the application is
> executed, and no console box appears, and the program becomes stuck in
> the cyg_libc_invoke_atexit_handlers() function (even when no return(),
> or exit() function calls are made when using the cyg_user_start()
> function and not the main() function).
When your main_program function exits, the scheduler will start, and start
a main().
> Is there a way to get the console up, or is it expected behaviour on the
> Cygwin compiled copy of GDB/Insight?
View->Console in Insight.
> And how can I get the program to
> not hang in this function call?
It's probably because a breakpoint has been set at "exit". At a guess.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine