Description of problem: Ah...I just compiled Linux Kernel 3.7.4, then...it happened... Version-Release number of selected component: cpp-4.7.2-8.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/gcc/x86_64-redhat-linux/4.7.2/cc1 -quiet -nostdinc -I /home/gch/software/linux-3.7.4/arch/x86/include -I arch/x86/include/generated -I include -I /home/gch/software/linux-3.7.4/arch/x86/include/uapi -I arch/x86/include/generated/uapi -I /home/gch/software/linux-3.7.4/include/uapi -I include/generated/uapi -I include/drm -D __KERNEL__ -D CONFIG_AS_CFI=1 -D CONFIG_AS_CFI_SIGNAL_FRAME=1 -D CONFIG_AS_CFI_SECTIONS=1 -D CONFIG_AS_FXSAVEQ=1 -D CONFIG_AS_AVX=1 -D CC_USING_FENTRY -D CC_HAVE_ASM_GOTO -D MODULE -D KBUILD_STR(s)=#s -D KBUILD_BASENAME=KBUILD_STR(ast_post) -D KBUILD_MODNAME=KBUILD_STR(ast) -isystem /usr/lib/gcc/x86_64-redhat-linux/4.7.2/include -include /home/gch/software/linux-3.7.4/include/linux/kconfig.h -MD drivers/gpu/drm/ast/.ast_post.o.d drivers/gpu/drm/ast/ast_post.c -quiet -dumpbase ast_post.c -m64 -mtune=generic -mno-red-zone -mcmodel=kernel -maccumulate-outgoing-args -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -mfentry -march=x86-64 -auxbase-strip drivers/gpu/drm/ast/ast_post.o -g -O2 -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -Werror=implicit-function-declaration -Wno-format-security -Wno-sign-compare -Wframe-larger-than=2048 -Wno-unused-but-set-variable -Wdeclaration-after-statement -Wno-pointer-sign -p -fno-strict-aliasing -fno-common -fno-delete-null-pointer-checks -funit-at-a-time -fstack-protector -fno-asynchronous-unwind-tables -fno-omit-frame-pointer -fno-optimize-sibling-calls -fno-strict-overflow -fconserve-stack -o - crash_function: open_memstream executable: /usr/libexec/gcc/x86_64-redhat-linux/4.7.2/cc1 kernel: 3.6.10-4.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #508 open_memstream at memstream.c:78 #509 __vsyslog_chk at ../misc/syslog.c:167 #510 __vsyslog at ../misc/syslog.c:324 #511 __libc_message at ../sysdeps/unix/sysv/linux/libc_fatal.c:167
Created attachment 688668 [details] File: backtrace
Created attachment 688669 [details] File: build_ids
Created attachment 688670 [details] File: cgroup
Created attachment 688671 [details] File: core_backtrace
Created attachment 688672 [details] File: dso_list
Created attachment 688673 [details] File: environ
Created attachment 688674 [details] File: limits
Created attachment 688675 [details] File: maps
Created attachment 688676 [details] File: open_fds
Created attachment 688677 [details] File: proc_pid_status
Created attachment 688678 [details] File: var_log_messages
All this info is useless if you can't reproduce it or if you don't provide reproducer. See http://gcc.gnu.org/bugs.html for what information is needed.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
I'm really sorry about this :-( It was just something wrong with my computer.
I found that bugzilla is sending me the needinfo requests all these years.So I made this comment just hoping to clean the needinfo flag:-).