public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Wilson Kwan" <wilson@kinesphere.com>
To: "Olaf Peters" <olaf.peters@technolution.nl>,
	<ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] GDB stubs on EDB7211
Date: Wed, 07 Feb 2001 08:20:00 -0000	[thread overview]
Message-ID: <013b01c09122$1d2c6c20$0b02a8c0@r2d2> (raw)
In-Reply-To: <JGEEJKHHJODGMOKKPBENAENGCAAA.olaf.peters@technolution.nl>

Hi Olaf,

> With this gdb_module.bin I get all kinds of errors when I try to debug the
> hello.c example program ("arm-elf-gdb -nw hello.exe" from a cygwin prompt
on
> win2000). I download the hello.exe program via the gdb load cmd and than
do
> e.g. stepi or cont. In both cases (stepi and cont) I get random results,
> sometimes a SIGTRAP, sometimes a SIGBUS, and I also experienced some
> 'Spurious interrupt' messages.

I also had problems like this. To fix this problem you should build the
stubs as one target and the main eCos kernel library as another (ie. two
configuration files). This will create two sets of directories for your
targets. I found that sometimes things behaved strangely if I used the same
configuration for both the library and stub builds. You can also try
deleting the <target>_build, <target>_install, and <target>_mlt directories
before you do a rebuild. This often fixes things for me. It seems the clean
option doesn't fully clean things out but I haven't verified this.

On the hardware side make sure you turn the board off and on again after a
SIGBUS error. This seems to help for me when I get this error.

Good luck,

Wilson

      parent reply	other threads:[~2001-02-07  8:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-07  5:54 Olaf Peters
2001-02-07  6:01 ` Lewin A.R.W. Edwards
2001-02-08  3:08   ` Olaf Peters
     [not found]   ` <JGEEJKHHJODGMOKKPBENOENLCAAA.olaf.peters@technolution.nl>
2001-02-08  6:55     ` Lewin A.R.W. Edwards
2001-02-07  8:20 ` Wilson Kwan [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='013b01c09122$1d2c6c20$0b02a8c0@r2d2' \
    --to=wilson@kinesphere.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=olaf.peters@technolution.nl \
    /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).