Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Marcus Gustafsson <marcus.gustafsson@kreatel.se>
Cc: linux-mips@linux-mips.org
Subject: Re: Busybox v0.60.2 insmod gives segmentation fault without any m essages when trying to load a loadable module
Date: Tue, 17 Aug 2004 20:08:06 +0200	[thread overview]
Message-ID: <20040817180806.GA14578@linux-mips.org> (raw)
In-Reply-To: <5BB336130A66D7119DEF009027463C2C0F2CDA@BERNTSSON>

On Tue, Aug 17, 2004 at 09:24:49AM +0200, Marcus Gustafsson wrote:

> Im using gcc-3.3.3 and busybox-0.60.5 and insmod works if I strip the debug
> symbols from the module.

Seems that insmod is derived from an awfully old version from kernel.org;
this bug was fixed years ago.

  Ralf

  reply	other threads:[~2004-08-17 18:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17  7:24 Busybox v0.60.2 insmod gives segmentation fault without any m essages when trying to load a loadable module Marcus Gustafsson
2004-08-17 18:08 ` Ralf Baechle [this message]
2004-08-17 19:49   ` David Daney
2004-08-17 22:24     ` Ralf Baechle

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=20040817180806.GA14578@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=marcus.gustafsson@kreatel.se \
    /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