From: Philip Teng <tcheewan@dso.org.sg>
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Running hello.c on i386
Date: Tue, 06 Feb 2001 23:11:00 -0000 [thread overview]
Message-ID: <3A80F870.8BA24E06@dso.org.sg> (raw)
I tried to make hello.c using the Makefile given in the /examples.
bash.exe-2.04$ make hello.o
i386-elf-gcc -c -o hello.o -g -Wall
-I//c/us
ers/philip/ecos/stub1_install/include -ffunction-sections
-fdata-sections hello.
c
hello.c:2: stdio.h: No such file or directory
make: *** [hello.o] Error 1
I encountered some errors and I fixed it by adding one more include
path...
bash.exe-2.04$ make hello.o
i386-elf-gcc -c -o hello.o -g -Wall
-I//c/us
ers/philip/ecos/stub1_install/include -I/usr/include -ffunction-sections
-fdata-
sections hello.c
bash.exe-2.04$
The compilation was successful. The target I used is a PIII machine,
host is Windows NT. I started up the i386 target using the gdb stub
floppy and run the following:
bash.exe-2.04$ i386-elf-gdb -nw hello.o
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
0x37dc in ?? ()
(gdb) continue
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x37dc in ?? ()
Anyone has any idea why the program hit a stop?
Philip Teng
DSO National Labs
tcheewan@dso.org.sg
next reply other threads:[~2001-02-06 23:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 23:11 Philip Teng [this message]
2001-02-09 12:08 ` Bart Veer
2001-02-11 17:09 ` Teng Chee Wan Philip
-- strict thread matches above, loose matches on Subject: below --
2001-02-05 5:16 JITENDRA kanitkar
2001-02-05 11:05 ` 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=3A80F870.8BA24E06@dso.org.sg \
--to=tcheewan@dso.org.sg \
--cc=ecos-discuss@sourceware.cygnus.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).