public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Pavel Machek <pavel@denx.de>,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	Hung Tran <hung.tran.jy@renesas.com>,
	cip-dev <cip-dev@lists.cip-project.org>
Subject: ldconfig segfault on RZ/Five was Re: Preparing isar-cip-core for RZ/Five
Date: Fri, 7 Oct 2022 00:07:40 +0200	[thread overview]
Message-ID: <20221006220740.GA7670@duo.ucw.cz> (raw)
In-Reply-To: <4d6db8d8-3d96-6969-f551-baa94f865fa3@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]

Hi!

> >> Hmm, seems the issue persists:
> > 
> > :-(. Do you get gcc faulting, too?
> 
> I tried, but installation fails - illegal instruction.

Yeah, ldconfig is needed for installation. But I get a segfaulting gcc
binary.

> >> root@demo:~# ldconfig                                                                        
> >>
> >> [  297.146728] ldconfig[497]: unhandled signal 4 code 0x1 at 0x00000000000380c8 in ldconfig[10000+83000]
> > ...
> >> (gdb) disassemble $pc,+0x10
> >> Dump of assembler code from 0x380c8 to 0x380d8:
> >> => 0x00000000000380c8:  auipc   a2,0x66
> >>    0x00000000000380cc:  addi    a2,a2,2000 # 0x9e898
> >>    0x00000000000380d0:  sd      a0,0(a2)
> > 
> > auipc is something rather simple. a2 = pc + 0x66 << something. Not
> > sure how it could fault. Plus we get "illegal instruction", suggesting
> > it is not some other fault.
> > 
> > Could some kind of self-modifying code be involved? I guess some kind
> > of debugging/watchpoint is not probable.
> 
> No idea - but why should ldconfig be self-modifying?

No idea.

But I do have slightly different results then you (I think; I'm far
from risc-v expert). I did a breakpoint:

Breakpoint 1, 0x00000000000385d4 in ?? ()
(gdb)

Dump of assembler code from 0x385d4 to 0x385f4:
=> 0x00000000000385d4:  lb      zero,81(t1)
   0x00000000000385d8:  andi    a1,a1,25
   0x00000000000385da:  sd      zero,24(sp)
   0x00000000000385dc:  sd      zero,32(sp)

If I do the stepi, it will give the illegal instruction, because,
well, we are in the middle of the auipc instruction:

(gdb) disassemble $pc-0x10,+0x20
Dump of assembler code from 0x385c4 to 0x385e4:
   0x00000000000385c4:  .4byte  0x4881f753
   0x00000000000385c8:  li      a6,0
   0x00000000000385ca:  li      a5,0
   0x00000000000385cc:  addi    a3,a1,920
   0x00000000000385d0:  mv      a2,s8
   0x00000000000385d2:  auipc   a0,0x3f
   0x00000000000385d6:  addi    a0,a0,-1890 # 0x76e70
   0x00000000000385da:  sd      zero,24(sp)
   0x00000000000385dc:  sd      zero,32(sp)
   0x00000000000385de:  sb      t3,20(sp)
   0x00000000000385e2:  sd      s7,40(sp)
End of assembler dump.
(gdb)

Weird. But it explains sigill when executing auipc does not result in
segfault...

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-10-06 22:07 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 18:36 Preparing isar-cip-core for RZ/Five Jan Kiszka
2022-10-03 20:12 ` Chris Paterson
2022-10-04  7:15   ` Jan Kiszka
2022-10-04 18:28     ` Jan Kiszka
2022-10-04 19:36       ` Jan Kiszka
2022-10-04 19:47         ` Jan Kiszka
2022-10-05 18:21           ` Pavel Machek
2022-10-06  6:29             ` Jan Kiszka
2022-10-06  6:49               ` Jan Kiszka
2022-10-06  7:07                 ` Jan Kiszka
2022-10-06  7:08                 ` Prabhakar Mahadev Lad
2022-10-06  7:26                   ` Jan Kiszka
2022-10-06 11:43               ` Pavel Machek
2022-10-06 11:51                 ` Jan Kiszka
2022-10-06 22:07                   ` Pavel Machek [this message]
2022-10-06 22:32                     ` ldconfig segfault on RZ/Five was " Pavel Machek
2022-10-07  8:18                       ` Jan Kiszka
2022-10-07 10:19                         ` Pavel Machek
2022-10-08  8:27                           ` Jan Kiszka
2022-10-09  8:29                             ` Jan Kiszka
2022-10-09  8:42                               ` [cip-dev] " Biju Das
2022-10-11  9:30                                 ` Jan Kiszka
2022-10-11 10:34                                   ` Biju Das
2022-10-11 18:51                                     ` Florian Bezdeka
2022-10-11 20:15                                       ` Jan Kiszka
2022-10-11 20:48                                         ` Prabhakar Mahadev Lad
2022-10-12  9:50                                           ` Prabhakar Mahadev Lad
2022-10-13  8:36                                             ` Ulrich Hecht
2022-10-13 10:35                                               ` Pavel Machek
2022-10-13 21:47                                               ` Pavel Machek
2022-11-29 18:57                                                 ` Prabhakar Mahadev Lad
2022-12-10  7:23                                                   ` Jan Kiszka
2022-12-10 20:25                                                     ` Pavel Machek
2022-12-12 13:51                                                       ` Prabhakar Mahadev Lad
2022-12-12 13:24                                                     ` Prabhakar Mahadev Lad
2022-10-09 19:20                               ` Chris Paterson
2022-10-05  5:43       ` [cip-dev] " Biju Das
2022-10-04 22:30   ` Prabhakar Mahadev Lad
2022-10-05  5:45     ` Jan Kiszka

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=20221006220740.GA7670@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=Chris.Paterson2@renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=hung.tran.jy@renesas.com \
    --cc=jan.kiszka@siemens.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    /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