From: "Ling Su" <lingsu@palmmicro.com>
To: "Jonathan Larmour" <jlarmour@redhat.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] GDB stubs build problem for vrc4373
Date: Wed, 31 Jan 2001 13:41:00 -0000 [thread overview]
Message-ID: <00d601c08bce$75358720$0201a8c0@raccoon> (raw)
In-Reply-To: <20010131151911.A14768@sr1.open-widgets.com>
One problme bothers me is, I have never succeeded in building a GDB stub for
vrc4373 by using a CVS version snapshot. Actually only the binary version
provided in eCos 1.3.1 release works for me, whenver I tried to build a new
one by using the CVS version or any snapshot of source code, I just got a
dead monitor without any response. Basically I did "ecosconfig new vrc4373
stubs" and then make it. I was really puzzled me whether the CVS version (or
the Open Sourced version) really the same as what RedHat playing with. Or we
really need to buy a comercialzed GNUPro toolchain to make the compiled code
working. I can compile my code starting up in RAM and debug it using the
binary GDB stub provided in eCos1.3.1 release, but why I can not make a
working GDB stub by myself? Anything I missed?
As you may know, I am trying to port the vrc4373 code to vrc4375 board, the
most important thing is to get a running stub, I want to make sure I can
build a working gdb stub for vrc4373 before I can change it to working on
vrc4375 board. I have been trying this for several days, no outcome. Any
advices? Thanks, and help, please... :-/
Regards,
-Ling
prev parent reply other threads:[~2001-01-31 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 14:45 [ECOS] Turn off gdb console? bgat
2001-01-30 19:07 ` Jonathan Larmour
2001-01-31 13:19 ` bgat
2001-01-31 13:41 ` Ling Su [this message]
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='00d601c08bce$75358720$0201a8c0@raccoon' \
--to=lingsu@palmmicro.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).