From: liuduo <liuduo@sinosoft.com.cn>
To: linux-ia64@vger.kernel.org
Subject: a question about memory access on IA64
Date: Fri, 16 Jan 2004 03:03:00 +0000 [thread overview]
Message-ID: <40075464.6010202@sinosoft.com.cn> (raw)
Dear Sir:
nice to see you !
here is a problem about accessing memory on IA64 as follows,
we define a structrue is :
typedef struct b{
unsigned short b1;
unsigned short b2;
unsigned char b3;
unsigned char b4;
unsigned char b5;
unsigned char b6;
}B;
typedef struct a{
struct b bb[512];
int c;}A;
when we use the struct A on IA64, the segmentation fault occurs ,
and then we modify the struct A as follows :
typedef struct a{
int c;
struct b bb[512];
}A;
we can use it normally .
can you explain why ?
thanks a lot , and expect your reply urgently
yours : calis
--
===================Liu duo
tel:(010)62570007-509
email:liuduo@sinosoft.com.cn
Sinosoft Software.Co.Ltd.
Esmpro Group.Secic Department
===================
next reply other threads:[~2004-01-16 3:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 3:03 liuduo [this message]
2004-01-16 3:16 ` a question about memory access on IA64 David Mosberger
2004-01-16 3:56 ` liuduo
2004-01-16 4:16 ` Martin Pool
2004-01-16 4:59 ` David Mosberger
2004-01-16 7:01 ` Martin Pool
2004-01-16 7:12 ` liuduo
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=40075464.6010202@sinosoft.com.cn \
--to=liuduo@sinosoft.com.cn \
--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