Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Rainer Weikusat Newsgroups: comp.os.linux.development.system Subject: Re: how to debug a kernel crash, using only the syslog dump? Date: Tue, 26 Jul 2011 11:37:20 +0100 Lines: 8 Message-ID: <877h75iazj.fsf@sapphire.mobileactivedefense.com> References: <4167f1de-0d78-4a29-934e-d77609f722a8@r5g2000prf.googlegroups.com> <2b201335-30e4-403a-bd83-0bb7f9a2a28f@h25g2000prf.googlegroups.com> <5441f84a-4889-4c26-9a8a-082a60f2b635@u6g2000prc.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: individual.net Vh1A9lkgMErXNkNoLTYRZwWxZcvUlaDT6IPvG1Ruknf5st1Og= Cancel-Lock: sha1:/wmaTXbfCdGlTVLF35jmShwDG5M= sha1:ntJTAkaZJYO+3XS9Vtb4sg/E5g8= User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.development.system:242 Gorlash writes: [...] > BTW, I rebuilt with '-g -o0', which isn't trivial in the mangled gcc > that Linux uses for building kernel code, Linux doesn't use 'a mangled gcc' for building kernel code.