From: alan on
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.

--
Truth is stranger than fiction because fiction has to make sense.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Américo Wang on
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.

What does 'file the_core_file_your_got' say?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Michal Marek on
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Alan on
On Fri, 2010-06-04 at 09:22 +0200, Michal Marek wrote:
> 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?

Don't know if this will help much.

This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols
from /home/alan/GitTrees/linux-2.6-mid-ref/scripts/mod/modpost...(no
debugging symbols found)...done.
(gdb) r
Starting
program: /home/alan/GitTrees/linux-2.6-mid-ref/scripts/mod/modpost -o
Module.symvers -S vmlinux.o

Program received signal SIGSEGV, Segmentation fault.
0x0000000000403711 in main ()
(gdb) bt full
#0 0x0000000000403711 in main ()
No symbol table info available.

Trying to get it to compile with debugging info.



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Américo Wang on
On Mon, Jun 07, 2010 at 09:59:39AM -0700, Alan wrote:
>On Fri, 2010-06-04 at 09:22 +0200, Michal Marek wrote:
>> 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?
>
>Don't know if this will help much.
>
>This GDB was configured as "x86_64-redhat-linux-gnu".
>For bug reporting instructions, please see:
><http://www.gnu.org/software/gdb/bugs/>...
>Reading symbols
>from /home/alan/GitTrees/linux-2.6-mid-ref/scripts/mod/modpost...(no
>debugging symbols found)...done.
>(gdb) r
>Starting
>program: /home/alan/GitTrees/linux-2.6-mid-ref/scripts/mod/modpost -o
>Module.symvers -S vmlinux.o
>
>Program received signal SIGSEGV, Segmentation fault.
>0x0000000000403711 in main ()
>(gdb) bt full
>#0 0x0000000000403711 in main ()
>No symbol table info available.
>
>Trying to get it to compile with debugging info.
>

Try to append "-g" to HOSTCFLAGS in the top Makefile. ;)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/