Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: jsoe0708@tiscali.be
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Gcc-3.2 beside gcc-3.0: HOWTO?
Date: Tue, 3 Sep 2002 09:13:26 -0700	[thread overview]
Message-ID: <20020903161326.GI14634@tausq.org> (raw)
In-Reply-To: <3D3815BD0000B0C0@ocpmta5.be.tiscali.com>

> General Registers 0 - 31
> 00-03   0000000000000000  00000000103b7244  0000000010108064  00000000207f8000
                                              ^^^^^^^^^^^^^^^^ GR02, aka
                                              the return pointer

> Control Registers 0 - 31
> 00-03   0000000000000000  0000000000000000  0000000000000000  0000000000000000
> 04-07   0000000000000000  0000000000000000  0000000000000000  0000000000000000
> 08-11   0000000000000634  0000000000000000  00000000000000c0  0000000000000017
> 12-15   0000000000000000  0000000000000000  0000000000107000  0000000000000000
> 16-19   0000007be95ffc60  0000000000000000  0000000010108638  000000000fa11288
                                                                ^^^^^^^^^^^^^^^^
cr19 is the "IIR", this is the insn that caused the fault
in this case, this insn is stw r1,4(sr0,r29)


> 20-23   0000000010240224  0000000048030104  000000000004000e  0000000080000000
> 24-27   0000000000305000  0000000000305000  0000000000044021  00000000f0412000
> 28-31   0000000055555555  0000000055555555  000000001f1f8000  00000000103a8000
                            ^^^^^^^^^^^^^^^^ which looks quite bogus

> IIA Space                    = 0x0000000000000000
> IIA Offset                   = 0x000000001010863c
this is the "iaoq" -- the instruction pointer

> But where is iaoq (I do not found in linux/Documentation/parisc)?
> 
> here is what I got: grep 101080 /boot/System.map-2.4.19-pa9
> 10108000 T syscall_exit_rfi
> 10108064 t intr_return
> 10108078 t intr_check_resched
> 10108084 t intr_check_sig
> 10108090 t intr_restore

is this the system.map from the kernel you are building?
if it is, then intr_return is the calling function (one up in the
stack). the function that includes 1010863c is the one that one that's
causing the fault. that would be one place to look.

hth
randolph
--  
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

  reply	other threads:[~2002-09-03 16:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02 10:02 [parisc-linux] Gcc-3.2 beside gcc-3.0: HOWTO? jsoe0708
2002-09-02 14:56 ` jsoe0708
2002-09-02 15:21 ` Randolph Chung
2002-09-02 16:31   ` jsoe0708
2002-09-02 16:44     ` Randolph Chung
2002-09-03  5:47       ` jsoe0708
2002-09-03  7:05         ` Randolph Chung
2002-09-03 15:33           ` jsoe0708
2002-09-03 16:13             ` Randolph Chung [this message]
2002-09-04  9:00               ` jsoe0708

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=20020903161326.GI14634@tausq.org \
    --to=randolph@tausq.org \
    --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