internal compiler error: SIGSEGV [Was: 2.6.25-mm1]

On 04/18/2008 10:47 AM, Andrew Morton wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25/2.6.25-mm1/

Hi, I'm not sure by what was this caused.

LANG=en strace -fo strace_gcc.txt gcc -Wp,-MD,drivers/usb/class/.usblp.o.d -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/4.3/include -D__KERNEL__ -Iinclude -Iinclude2 -I/home/l/latest/xxx/include -include include/linux/autoconf.h -I/home/l/latest/xxx/drivers/usb/class -Idrivers/usb/class -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -O2 -fno-stack-protector -m64 -march=core2 -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -I/home/l/latest/xxx/include/asm-x86/mach-default -Iinclude/asm-x86/mach-default -fno-omit-frame-pointer -fno-optimize-sibling-calls -g -Wdeclaration-after-statement -Wno-pointer-sign -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(usblp)" -D"KBUILD_MODNAME=KBUILD_STR(usblp)" /home/l/latest/xxx/drivers/usb/class/usblp.c -S -o usblp.s
/home/l/latest/xxx/drivers/usb/class/usblp.c: In function 'usblp_submit_read':
/home/l/latest/xxx/drivers/usb/class/usblp.c:977: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.opensuse.org/> for instructions.




strace_gcc.txt:
http://www.fi.muni.cz/~xslaby/sklad/strace_gcc.txt

preprocessor output available here:
http://www.fi.muni.cz/~xslaby/sklad/usblp.E

Reboot fixed it. It happened after few suspend/resume cycles. The preproc output differs in no way from after the reboot. Now, the strace looks like:
5341 mmap(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f362e004000
5341 mmap(NULL, 1048576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f362df04000
5341 brk(0x1964000) = 0x1964000
5341 brk(0x194c000) = 0x194c000
5341 brk(0x196d000) = 0x196d000
5341 brk(0x195a000) = 0x195a000
5341 mmap(NULL, 143360, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f362dee1000
5341 munmap(0x7f362dee1000, 143360) = 0
5341 brk(0x1981000) = 0x1981000
5341 brk(0x196b000) = 0x196b000
5341 brk(0x1966000) = 0x1966000
5341 mmap(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f362defc000
5341 brk(0x1988000) = 0x1988000

at that sigsegv place.

Some kind of random-brk gcc (gcc-4.3-30) non-readiness?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: Error in Preprocessing
    ... Dan.) ... (it is necessary for the program correctness, but not if the program is ... only preprocessed, as it will generate tons of preprocessor output), ...
    (comp.lang.c)
  • Re: #defines and enumerations in Java - How ?
    ... Tilman Bohn wrote: ... > compiler, but are exclusively and completely handled by the preprocessor. ... > The compiler only ever sees the preprocessor output. ...
    (comp.lang.java.programmer)
  • Re: what is .i file?
    ... SM Ryan wrote: ... > Intermediate file between the C preprocessor and the C compiler. ... the .i file is usually only written when the preprocessor output ...
    (comp.lang.cpp)
  • Re: what is .i file?
    ... SM Ryan wrote: ... > Intermediate file between the C preprocessor and the C compiler. ... the .i file is usually only written when the preprocessor output ...
    (comp.unix.programmer)
  • Re: what is .i file?
    ... SM Ryan wrote: ... > Intermediate file between the C preprocessor and the C compiler. ... the .i file is usually only written when the preprocessor output ...
    (comp.lang.c)