From: jsoe0708@tiscali.be
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Back to evms-1.0.1 && unaligne access && gdb
Date: Thu, 29 Aug 2002 18:59:07 +0200 [thread overview]
Message-ID: <3D53B3B70000896D@ocpmta1.be.tiscali.com> (raw)
In-Reply-To: <200208291428.g7TESm9l024111@hiauly1.hia.nrc.ca>
>-- Original Message --
>Subject: Re: [parisc-linux] Back to evms-1.0.1 && unaligne access && gdb
>To: jsoe0708@tiscali.be
>From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
>Cc: parisc-linux@lists.parisc-linux.org
>Date: Thu, 29 Aug 2002 10:28:48 -0400 (EDT)
>
>
>> >Program received signal SIGINT, Interrupt.
>> >0x4020a0e4 in isa_null_partition_record (p=0x3fe0ff) at checks.c:65
>
>You can see from the value of p above that it is not properly aligned
>for a 4 byte access. Put a break on isa_null_partition_record and
>
>cond n p==0x3fe0ff
>
>where n is the breakpoint number of the break at isa_null_partition_record.
As previously, I could not put a break at isa_null_partition_record (function
not define but with ^C I reach to stop recursively in this function and so
for example with p==0x26ece I got p.boot_ind=0 ; p.head=63 ; p.sector=224
; p.cyl=255; ...
p is of type partition define as follow:
struct partition {
unsigned char boot_ind; /* 0x80 - active */
unsigned char head; /* starting head */
unsigned char sector; /* starting sector */
unsigned char cyl; /* starting cylinder */
unsigned char sys_ind; /* What partition type */
unsigned char end_head; /* end head */
unsigned char end_sector; /* end sector */
unsigned char end_cyl; /* end cylinder */
unsigned int start_sect; /* starting sector counting from 0 */
unsigned int nr_sects; /* nr of sectors in partition */
};
So anyway there is a bug because I presume that the for loop is there to
scan the 4 int what it doen't do (?) and find another way to say an 'int'
is null ( hmm why not simply
u_int8_t *uip = (u_int8_t *)p;
for (i=0 ; i<16 ; i++){
if (*uip+i != 0x00) return FALSE;
}
return TRUE;
what do you think?
>Then, run the program and it should stop at isa_null_partition_record
>when the fault is about to occur. You will then have to do a bt to
>determine why p is incorrectly aligned (last hex digit should be 0,
>4, 8 or c).
Many thanks,
Joel
next prev parent reply other threads:[~2002-08-29 16:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 9:22 [parisc-linux] Back to evms-1.0.1 && unaligne access && gdb 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2002-08-29 13:56 jsoe0708
2002-09-02 8:47 jsoe0708
2002-09-02 17:28 ` Grant Grundler
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=3D53B3B70000896D@ocpmta1.be.tiscali.com \
--to=jsoe0708@tiscali.be \
--cc=dave@hiauly1.hia.nrc.ca \
--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