[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1181390911.3306.22.camel@jcmlaptop>
Date: Sat, 09 Jun 2007 08:08:31 -0400
From: Jon Masters <jonathan@...masters.org>
To: Jan Engelhardt <jengelh@...putergmbh.de>
Cc: "Robert P. J. Day" <rpjday@...dspring.com>,
Kyle McMartin <kyle@...onical.com>,
Christoph Pleger <Christoph.Pleger@...uni-dortmund.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Size of kernel modules
On Sat, 2007-06-09 at 09:55 +0200, Jan Engelhardt wrote:
> On Jun 8 2007 08:40, Robert P. J. Day wrote:
> >>
> >> If you disable CONFIG_DEBUG_KERNEL, things should go back to normal
> >> sizes for you.
> >
> >grow so much compared to *which other modules*? the ones that came
> >with your distro? if that's the case, try installing your new modules
> >with
> >
> > # make INSTALL_MOD_STRIP=1 modules_install
> >
> >that makes a *huge* difference in the size of the installed modules,
> >as i learned when i first ran across this on my fedora core system.
>
> Definitely. Running depmod on debug-enabled .ko files explodes in a segfault
> after depmod allocates more and more and more memory (exhausting both
> my ram and swap).
So I missed half of this conversation - you're saying that on a
CONFIG_DEBUG_KERNEL, you have such large .ko module files that depmod
segfaults? Can I get a core dump or any further information? :-)
Jon.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists