public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: alan <alan@clueserver.org>, linux-kernel@vger.kernel.org
Subject: Re: Additional info on modpost segfault
Date: Fri, 04 Jun 2010 09:22:56 +0200	[thread overview]
Message-ID: <4C08A9D0.8000505@suse.cz> (raw)
In-Reply-To: <20100604045118.GC5167@cr0.nay.redhat.com>

On 4.6.2010 06:51, Américo Wang wrote:
> On Thu, Jun 03, 2010 at 08:10:30PM -0700, alan wrote:
>> Missed adding the actual segfault message:
>>
>>  LD      drivers/usb/built-in.o
>>  LD      drivers/built-in.o
>>  LD      vmlinux.o
>>  MODPOST vmlinux.o
>> /bin/sh: line 1: 20665 Segmentation fault      (core dumped)
>> scripts/mod/modpost -o
>> /home/alan/GitTrees/linux-2.6-mid-ref/Module.symvers -S vmlinux.o
>> make[1]: *** [vmlinux.o] Error 139
>> make: *** [vmlinux.o] Error 2
>>
>> I have looked at the gcc 4.4.4 changelog and I can't see anything
>> that should cause this.
>>
> 
> Hmm, you need to find which program segfaults here.

It's the modpost command run on vmlinux.o. Alan, can you try
$ gdb --args scripts/mod/modpost -o Module.symvers -S vmlinux.o
(gdb) r
(wait for the segfault)
(gdb) bt full

and post the backtrace?

Thanks,
Michal

  reply	other threads:[~2010-06-04  7:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-04  3:10 Additional info on modpost segfault alan
2010-06-04  4:51 ` Américo Wang
2010-06-04  7:22   ` Michal Marek [this message]
2010-06-07 16:59     ` Alan
2010-06-08  5:51       ` Américo Wang
2010-06-08 18:24         ` Alan
2010-06-09  8:35           ` Américo Wang
2010-06-10 23:08       ` Krzysztof Halasa
2010-06-11  0:06         ` alan
2010-06-11 20:42         ` H. Peter Anvin
2010-06-11 22:49           ` Michal Marek

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=4C08A9D0.8000505@suse.cz \
    --to=mmarek@suse.cz \
    --cc=alan@clueserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    /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