All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: linux-mips@oss.sgi.com
Subject: problems with insmod ...
Date: Fri, 20 Oct 2000 19:50:03 -0700	[thread overview]
Message-ID: <39F1045B.21EF1851@mvista.com> (raw)


I am using modutils v2.1.121, generated by binutils 2.8.1/egcs
v1.0.3a/glibc 2.0.6.

I have several problems with it.

In obj/obj_mipsel.c arch_apply_relocation() function, the mips_hi16_list
is not initialized to NULL before it is used as a list head.  So, later,
insmod dies at trying to access 0x41.

(BTW, it seems horrible to me that arch_apply_relocation() remaps
obj_file struct to a local mips_file struct, destroying the original ELF
header struct.  Is this safe?)

I kind of hacked around this problem (I don't know the real fix), but I
got some other problems.  This time it is at obj/obj_reloc.c:410 -
sec->contents is 0x0.  It seems to me that this section should be
included in load list at the first place.  Does somebody why it is
there?  

I dumped the section info here :

(gdb) p/x *f->load_order->load_next->load_next
$22 = {
  header = {
    sh_name = 0x36,
    sh_type = 0x70000006,
    sh_flags = 0x2,
    sh_addr = 0xc00000e0,
    sh_offset = 0xd0,
    sh_size = 0x18,
    sh_link = 0x0,
    sh_info = 0x0,
    sh_addralign = 0x4,
    sh_entsize = 0x1
  },
  name = 0x1001bf26,
  contents = 0x0,
  load_next = 0x1001bd88,
  idx = 0x5
}

=======

BTW, I seem to remember someone said the modutils 2.1.121 is not good
MIPS.  Which version is good?

Jun

             reply	other threads:[~2000-10-21  2:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-21  2:50 Jun Sun [this message]
2000-10-21  3:11 ` problems with insmod Ralf Baechle
2000-10-21  4:12 ` Keith Owens
2000-10-23 18:45   ` Jun Sun
2000-10-23 22:32     ` Keith Owens
2000-10-24  0:40       ` Ralf Baechle
2000-10-24  1:08         ` Jun Sun
2000-10-24  1:18           ` Ralf Baechle
2000-10-24  1:18             ` Ralf Baechle
2000-10-23 22:42     ` Brady Brown

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=39F1045B.21EF1851@mvista.com \
    --to=jsun@mvista.com \
    --cc=linux-mips@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.