public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Peter Blair" <peterb@turnpikeglobal.com>
To: "Jonathan Larmour" <jlarmour@redhat.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Problems with running applications
Date: Tue, 21 Aug 2001 13:20:00 -0000	[thread overview]
Message-ID: <8669764C0A96B640AE8A6F5BB7C259D955D6@turnpdcf1.home.turnpikeglobal.com> (raw)

I did load the application via GDB/Insight, just as you described in
your prior message.

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).
 
Is there a way to get the console up, or is it expected behaviour on the
Cygwin compiled copy of GDB/Insight?  And how can I get the program to
not hang in this function call?

Thanks again,
Peter Blair.

	-----Original Message----- 
	From: Jonathan Larmour 
	Sent: Tue 8/21/2001 3:36 PM 
	To: Peter Blair; eCos discussion 
	Cc: 
	Subject: Re: [ECOS] Problems with running applications
	
	

	
	You haven't loaded the program yet! Type "load" in the command
line, or
	from GDB, use Run->Download. Even easier: Use File->Target
Settings and
	choose the "More Options" arrow and select "Attach to Target"
and "Download
	Program".
	
	

             reply	other threads:[~2001-08-21 13:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-21 13:20 Peter Blair [this message]
2001-08-21 13:44 ` Jonathan Larmour
     [not found] <8669764C0A96B640AE8A6F5BB7C259D955D3@turnpdcf1.home.turnpikeglobal.com>
2001-08-21 12:36 ` Jonathan Larmour
  -- strict thread matches above, loose matches on Subject: below --
2001-08-21 12:25 Peter Blair
2001-08-21 12:02 Peter Blair
2001-08-21 12:07 ` Jonathan Larmour

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=8669764C0A96B640AE8A6F5BB7C259D955D6@turnpdcf1.home.turnpikeglobal.com \
    --to=peterb@turnpikeglobal.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jlarmour@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).