full-disclosure - gcc: Internal compiler error: program cc1 got fatal signal 11

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

From: tac at noldata.com (Noldata TAC)
Subject: gcc: Internal compiler error: program cc1
	got fatal signal 11

You must execute it:

glozano@...ssom:~$ more a.c
int main(void)
 {
 printf("%c","msux"[0xcafebabe]);
 }
glozano@...ssom:~$ make a
cc     a.c   -o a
glozano@...ssom:~$ ./a
Segmentation fault


On Thu, 2004-01-08 at 17:59, Dani Wuck wrote:
> user@...t:~$ echo 'int main(void)
>  > {
>  > printf("%c","msux"[0xcafebabe]);
>  > }'> ./gcc-crash.c
> user@...t:~$ gcc ./gcc-crash.c
> user@...t:~$
> 
> Not confirmed on Slackware 9.1 (patched kernel 2.4.24)
> GCC 3.2.3
> 
> Georgi Guninski wrote:
> 
> > $ gcc --version
> > 2.95.3
> > $ cat gcc-crash.c
> > int main(void)
> > {
> > printf("%c","msux"[0xcafebabe]);
> > }
> > $ gcc gcc-crash.c
> > gcc: Internal compiler error: program cc1 got fatal signal 11
> > 
> > _______________________________________________
> > Full-Disclosure - We believe in it.
> > Charter: http://lists.netsys.com/full-disclosure-charter.html
> > 
> 
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html
-- 
Noldata TAC <tac@...data.com>
Noldata Ltd.