From: Rusty Russell <rusty@rustcorp.com.au>
To: "Méher Khiari" <meher@wanadoo.fr>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [module-init-tools] Segmentation fault
Date: Wed, 21 Apr 2004 07:56:02 +1000 [thread overview]
Message-ID: <1082444781.5566.166.camel@bach> (raw)
In-Reply-To: <4083A05F.8060309@wanadoo.fr>
On Mon, 2004-04-19 at 19:48, Méher Khiari wrote:
> Hi all
> It is my first post here.
> I didn't find any other mailing list talking about module-init-tools
> (nor a wiki page), so I am posting here.
> I got module-init-tools-0.9.14, I compiled and installed (as written in
> the README) but I got a segmentation fault when I tested modprobe.
> Although, I got the testsuite and ran the test and all went well !!!!
Yes. The testsuite rebuilds the binaries with -DJUST_TESTING so it can
do nasty things to the internals (like control uname). These will
segfault if run normally. Hence "make check" now does a "make clean" at
the end.
Hope that helps!
Rusty.
--
Anyone who quotes me in their signature is an idiot -- Rusty Russell
prev parent reply other threads:[~2004-04-20 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 9:48 [module-init-tools] Segmentation fault Méher Khiari
2004-04-20 21:56 ` Rusty Russell [this message]
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=1082444781.5566.166.camel@bach \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=meher@wanadoo.fr \
/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