From: n0ano@indstorage.com
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] unaligned access?
Date: Wed, 28 Nov 2001 17:57:09 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805556@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805553@msgid-missing>
D'Laila-
Some basic IA64'isms:
The instruction pointer points to a bundle that
includes 3 instructions. All instruction bundles
are alligned on a 16-byte boundary.
The instruction pointer as reported by a signal trap frame
encodes both the bundle address and the specific instruction
inside the bundle that caused the fault. The specific
instruction is encoded in the lowest 4 bits of the bundle
address. In your situatation, the bundle address was at
0x4000000000003540 and the second instruction (encoded as 1)
in the bundle was the one that caused the fault.
Just anding off the lower 4 bits from `scp->sc_ip' will solve
your problem.
On Wed, Nov 28, 2001 at 09:37:51AM -0800, Pereira, D LailaX E wrote:
> HI
> While running the following code,
> define WRITE_CAUSED_SIGBUS_or_SEGV \
> (((*(unsigned long*)scp->sc_ip)>>21)&1)
> ....
> if (WRITE_CAUSED_SIGBUS_or_SEGV){
> ........
> }
> else {
> .........
> }
>
> I get the following error on the "if " statement:
> stress.udp(31438): unaligned access to
> 0x4000000000003541,ip=0x4000000000015fc1
> Please let me know what is wrong with the macro:
> define WRITE_CAUSED_SIGBUS_or_SEGV \
> (((*(unsigned long*)scp->sc_ip)>>21)&1)
>
>
> thanks
> d'laila
>
>
>
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@indstorage.com
Ph: 303/652-0870x117
next prev parent reply other threads:[~2001-11-28 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 17:37 [Linux-ia64] unaligned access? Pereira, D LailaX E
2001-11-28 17:47 ` Dan Pop
2001-11-28 17:56 ` Pereira, D LailaX E
2001-11-28 17:57 ` n0ano [this message]
2001-11-28 18:25 ` David Mosberger
2001-11-28 19:18 ` Dan Pop
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=marc-linux-ia64-105590698805556@msgid-missing \
--to=n0ano@indstorage.com \
--cc=linux-ia64@vger.kernel.org \
/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