From: Manish Lohani <mlohani@gmail.com>
To: linux-mips@linux-mips.org
Subject: Busybox v0.60.2 insmod gives segmentation fault without any messages when trying to load a loadable module
Date: Thu, 12 Aug 2004 10:30:32 -0700 [thread overview]
Message-ID: <b318a0150408121030389aa24c@mail.gmail.com> (raw)
I have a driver loadable module which i am compiling with the same gcc
flags as used to compile a kernel for a MIPS R5432 based NEC board.
On the development machine, to compile files driver1.c and driver2.c:
$ mips_fp_le-gcc -fomit-frame-pointer -fno-strict-aliasing -G 0
-mno-abicalls -fno-pic -pipe -mtune=r5000 -mlong-calls -mips2 -Wall -c
driver1.c
$mips_fp_le-ld -r -o driver --printmap --cref driver1.o driver2.o
mips_fp_le-gcc (GCC) version 3.3.1
mips_fp_le-ld (GNU ld) version 2.14
I have Busybox v0.60.2 on the target.
On the target:
# insmod ./driver
Using driver
Segmentation fault
#
Does anybody have any suggestions as to what could be wrong?
Thanks in advance,
Manu
next reply other threads:[~2004-08-12 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 17:30 Manish Lohani [this message]
2004-08-12 17:48 ` Busybox v0.60.2 insmod gives segmentation fault without any messages when trying to load a loadable module David Daney
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=b318a0150408121030389aa24c@mail.gmail.com \
--to=mlohani@gmail.com \
--cc=linux-mips@linux-mips.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