From: "Frank Ch. Eigler" <fche@redhat.com>
To: Shilin Shakti <shilins@KPITCummins.com>
Cc: cgen@sources.redhat.com
Subject: Re: Simulator Porting
Date: Wed, 25 May 2005 14:20:00 -0000 [thread overview]
Message-ID: <20050525142028.GA9705@redhat.com> (raw)
In-Reply-To: <4A1BE23A7B777442B60F4B4916AE0F1305B2E440@sohm.kpit.com>
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
Hi -
shilins wrote:
> [...] Am i doing all these correctly? Also what do you think might
> be the reason for that address alignment issue?
It's very hard to say. We may need to see code and other data. Check
your initialization and main loop code. Activate all available sim
tracing options. Run the gdb-linked variant of the simulator, so you
can single-step it under control.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-25 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 10:43 Shilin Shakti
2005-05-25 14:20 ` Frank Ch. Eigler [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-26 13:18 Shilin Shakti
2005-05-27 19:04 ` Frank Ch. Eigler
2005-05-24 7:31 Shilin Shakti
2005-05-24 6:58 Shilin Shakti
2005-05-24 12:59 ` Frank Ch. Eigler
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=20050525142028.GA9705@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=shilins@KPITCummins.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).