From: Grant Grundler <grundler@dsl2.external.hp.com>
To: jsoe0708@tiscali.be
Cc: "Joel Soete" <joel.soete@freebel.net>,
"John David Anglin" <dave@hiauly1.hia.nrc.ca>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Back to evms-1.0.1 && unaligne access && gdb
Date: Mon, 02 Sep 2002 11:28:54 -0600 [thread overview]
Message-ID: <20020902172854.C73F44829@dsl2.external.hp.com> (raw)
In-Reply-To: Message from jsoe0708@tiscali.be of "Mon, 02 Sep 2002 10:47:59 +0200." <3D3815BD0000A476@ocpmta5.be.tiscali.com>
jsoe0708@tiscali.be wrote:
> >Since start_sect and nr_sects are ints, this code will also generate an
> >"unaligned data reference fault" like the original code did.
>
> Trust me it does not? (it works fine)
then I'll wager there is padding between the char and int fields
of that struct.
> >You need
> >to find the origin of "struct partition *p" when the address is un-aligned.
> >
> Very hard to define:
> a. the previous code works (again all odds)
> b. the following trial code:
...
> int main(int argc, char * * argv, char * * env) {
>
> struct partition p1, p2;
...
> did not reproduce the problem.
Things on the stack (local var) are properly aligned.
Malloc a block of mem and then point to an unaligned address
in that block.
> What can I do to analyse this problem? (printing all p addresses and its
> elements
> during a run with the original code and compare with a run with modified
> code?)
yes. You want to verify the addreses are unaligned.
grant
next prev parent reply other threads:[~2002-09-02 17:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 8:47 [parisc-linux] Back to evms-1.0.1 && unaligne access && gdb jsoe0708
2002-09-02 17:28 ` Grant Grundler [this message]
2002-09-03 16:02 ` [parisc-linux] Unaligne access [was: Back to evms-1.0.1 && unaligne access && gdb ] jsoe0708
2002-09-03 20:33 ` [parisc-linux] " Grant Grundler
2002-09-04 7:14 ` jsoe0708
2002-09-04 11:48 ` jsoe0708
2002-09-03 20:44 ` John David Anglin
2002-09-04 6:45 ` jsoe0708
2002-09-04 14:55 ` Randolph Chung
-- strict thread matches above, loose matches on Subject: below --
2002-08-29 13:56 [parisc-linux] Back to evms-1.0.1 && unaligne access && gdb jsoe0708
2002-08-29 9:22 jsoe0708
2002-08-29 9:51 ` jsoe0708
2002-08-29 14:16 ` John David Anglin
2002-08-29 14:21 ` jsoe0708
2002-08-29 14:28 ` John David Anglin
2002-08-29 16:59 ` jsoe0708
2002-08-29 17:10 ` John David Anglin
2002-08-30 5:46 ` jsoe0708
2002-08-30 17:03 ` John David Anglin
2002-08-31 21:23 ` Joel Soete
2002-08-31 23:50 ` Grant Grundler
2002-08-29 17:12 ` jsoe0708
2002-08-29 18:11 ` Grant Grundler
2002-08-30 5:53 ` jsoe0708
2002-08-30 6:30 ` Grant Grundler
2002-08-30 6:42 ` jsoe0708
2002-08-29 12:42 ` Carlos O'Donell
2002-08-29 14:11 ` John David Anglin
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=20020902172854.C73F44829@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=joel.soete@freebel.net \
--cc=jsoe0708@tiscali.be \
--cc=parisc-linux@lists.parisc-linux.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