From: "Koeller, T." <Thomas.Koeller@baslerweb.com>
To: 'eCos mailing list' <ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] cannot get insight to work
Date: Wed, 24 Jan 2001 09:14:00 -0000 [thread overview]
Message-ID: <850597605E79D21182830008C7A4B9CF07D88604@COMM1> (raw)
I wonder if someone can help me with the problem described below:
I am building the sample application 'hello.c' on a Cygwin (Windows NT) host
for a PC target. Everything appears to work, 'hello.exe' is generated
without errors. I then boot the target system from a floppy containing a gdb
stubs program I built before. Next, I start Insight (i386-elf-gdb) and set
up the target serial port parameters. Up to this point, everything appears
to work. Then I load my debug executable 'hello.exe'. This also does not
give any errors, but no source code is displayed, even though the source
file is in the same directory as the executable. If I then hit either 'Run'
or 'Download', I get 'Request to download non-existent executable
/ecos-example/hello.exe'. When I select 'hello.c' from the 'current file
name' combo box, I get 'Error: couldn't stat "/ecos-example/hello.c": no
such file or directory'.
-----------------------------------------------
Thomas Koeller, Software Development
Basler Vision Technologies
An der Strusbek 60-62
22926 Ahrensburg
Germany
Tel +49 (4102) 463-390
Fax +49 (4102) 463-109
mailto:Thomas.Koeller@baslerweb.com
http://www.baslerweb.com
next reply other threads:[~2001-01-24 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 9:14 Koeller, T. [this message]
2001-01-24 11:14 ` Jonathan Larmour
2001-01-25 1:21 Koeller, T.
2001-01-25 9:48 ` 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=850597605E79D21182830008C7A4B9CF07D88604@COMM1 \
--to=thomas.koeller@baslerweb.com \
--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).