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 for Android: free password hash cracker in your pocket

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

Message-ID: <20040109004626.GA18745@ssc.com>
From: dan at ssc.com (Dan Wilder)
Subject: gcc: Internal compiler error: program cc1 got fatal signal 11

On Thu, Jan 08, 2004 at 11:52:36PM +0000, Luke Norman wrote:

> $ gcc --version
> gcc (GCC) 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r3, propolice)
> Copyright (C) 2002 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> $ cat gcc-crash.c
> int main(void)
> {
> printf("%c","msux"[0xcafebabe]);
> }
> $ gcc gcc-crash.c
> $ ./a.out
> Segmentation fault

That's what I'd hope it did.  On the other hand, using either
of our compilers,

$ cat no-crash.c
int main(void)
{
printf("%c\n","msux"[3]);
}
$ gcc no-crash.c
$ ./a.out
x

-- 
Dan Wilder