From: "Frank Ch. Eigler" <fche@redhat.com>
To: T Satish Kumar <satish@td.idc.lsi.sanyo.co.jp>
Cc: Keith Seitz <keiths@redhat.com>, sid@sources.redhat.com
Subject: Re: Fw: [ECOS] how to build an eCos library for ARM7tdmi simulator
Date: Wed, 18 Sep 2002 19:05:00 -0000 [thread overview]
Message-ID: <20020918220533.B24977@redhat.com> (raw)
In-Reply-To: <001501c25ff2$7cc84820$19b6b486@sltisatish>; from satish@td.idc.lsi.sanyo.co.jp on Thu, Sep 19, 2002 at 08:37:39AM -0700
Hi -
On Thu, Sep 19, 2002 at 08:37:39AM -0700, T Satish Kumar wrote:
> well, No, even after running
> 1. arm-elf-sid --board=pid7t-normalmap --gdb=2000 -EL &
> 2.arm-elf-gdb -nw twothreads.x
> 3. target remote localhost:2000
> i get a message displaying:
>
> localhost:2000 Attempt to connect timed out with out establishing a
> connection.
>
> well, incase i run arm-elf-sid with --tksm option , i get a stackdump (i.e
> sid.exe.stackdump)
Neither of these two failures sound familiar. Perhaps you have a
misbuilt or misinstalled simulator, or some other unique problem.
For the first case, try adding "-v" to the arm-elf-sid command
line: it will produce lots of tracing output, the tail end of which
should give some hint about what's going wrong. Try a TCP port
number other than 2000. You can try catching sid's crash under a
debugger, if you first "arm-elf-sid --no-run [other-options]",
then run sid directly under the debugger: "gdb -args sid sid.conf"/"run"
or somesuch.
> i m not able to proceed further after this in either cases..
> someone plz help me at the earliest..
For what it's worth, Red Hat offers support contracts on its
software, which entitle customers to more in-depth help than
you might have reason to expect here.
- FChE
next prev parent reply other threads:[~2002-09-19 2:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0209180912590.1392-100000@valrhona.uglyboxes.com>
2002-09-18 16:37 ` T Satish Kumar
2002-09-18 19:05 ` Frank Ch. Eigler [this message]
2002-09-18 19:02 ` T Satish Kumar
2002-09-18 19:03 T Satish Kumar
2002-09-19 1:31 T Satish Kumar
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=20020918220533.B24977@redhat.com \
--to=fche@redhat.com \
--cc=keiths@redhat.com \
--cc=satish@td.idc.lsi.sanyo.co.jp \
--cc=sid@sources.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).