From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Peter Blair" <peterb@turnpikeglobal.com>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Problems with running applications
Date: Tue, 21 Aug 2001 12:25:00 -0000
Message-id: <8669764C0A96B640AE8A6F5BB7C259D955D5@turnpdcf1.home.turnpikeglobal.com>
X-SW-Source: 2001-08/msg00704.html

I've tried that, and this time I attempted to connect without using
insight-- 
<--snip-->

	$ i386-elf-gdb -nw test.exe
	GNU gdb 5.0
	Copyright 2000 Free Software Foundation, Inc.
	GDB is free software, covered by the GNU General Public License,
and you are
	welcome to change it and/or distribute copies of it under
certain conditions.
	Type "show copying" to see the conditions.
	There is absolutely no warranty for GDB.  Type "show warranty"
for details.
	This GDB was configured as "--host=i686-pc-cygwin
--target=i386-elf"...
	(gdb) set remotebaud 38400
	(gdb) target remote com1
	Remote debugging using com1
	0x97a8 in ?? ()
	    at
/ecos/ecos/packages/language/c/libc/startup/current/src/atexit.cxx:115
	115             return 1; // failure
	(gdb)
	<--end snip-->
	 
	As you can see, I'm faced with this error whenever I transfer
without insight.  Yet with insight, the transfer appears to go without a
hitch.
	 
	Side-Note:  Whenever running GDB/Insight with my native gcc/gdb,
a console pops up with the output of my program.  From your previous
message, I would believe that a simillar box should appear with eCos'
stdout, but no such box appears.
	 
	-Pete. 

		-----Original Message----- 
		From: Jonathan Larmour 
		Sent: Tue 8/21/2001 3:07 PM 
		To: Peter Blair 
		Cc: ecos-discuss@sources.redhat.com 
		Subject: Re: [ECOS] Problems with running applications
		

		
		> Is eCos' stdout the screen, a serial port on the
target machine, or
		> somewhere in gdb?
		
		If you loaded over serial via GDB, the output should
come over the serial
		via GDB. What if you just have:
		
		-=-=-=-=-
		#include <stdio.h>
		int main(){
		  printf("Testing, 1-2-3\n");
		  return 0;
		}
		-=-=-=-=-