From: Cristiano Ligieri Pereira <cpereira@ics.uci.edu>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Another port problem
Date: Thu, 16 Aug 2001 23:13:00 -0000 [thread overview]
Message-ID: <Pine.SOL.4.20.0108162303410.1173-100000@washoe.ics.uci.edu> (raw)
In-Reply-To: <3B7C51A5.877A0117@redhat.com>
The addresses seem OK. Even without remapping the problem keeps
happening... even though I don't understand why it doesn't crash when
copying the vectors to 0x0.
> The obvious guess is that you're hitting a bad address (due to the
> remapping potentially) and it's going wrong. You'd have to put something in
> the abort_data VSR to find out what address. You can't easily use C of
> course, because your BSS isn't set up :).
>
> Jifl
> --
> Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
> Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
>
prev parent reply other threads:[~2001-08-16 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 15:39 Cristiano Ligieri Pereira
2001-08-16 16:05 ` Jonathan Larmour
2001-08-16 23:13 ` Cristiano Ligieri Pereira [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=Pine.SOL.4.20.0108162303410.1173-100000@washoe.ics.uci.edu \
--to=cpereira@ics.uci.edu \
--cc=ecos-discuss@sourceware.cygnus.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).