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: <20040109135328.O72826@dekadens.coredump.cx>
From: lcamtuf at ghettot.org (Michal Zalewski)
Subject: gcc: Internal compiler error: program cc1 got
 fatal signal 11

On Thu, 8 Jan 2004, Roy M. Silvernail wrote:

> mesmer tmp $ gcc --version
> gcc (GCC) 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice)

It seems that the most recent GCC releases do not share this problem (not
all that surprisingly, given the nature of changes between the versions);
2.x releases, OTOH, are plagued by many different compile-time crash
vectors, or constructions that lead to invalid code - this one is not
an exception...

-- 
------------------------- bash$ :(){ :|:&};: --
 Michal Zalewski * [http://lcamtuf.coredump.cx]
    Did you know that clones never use mirrors?
--------------------------- 2004-01-09 13:53 --

   http://lcamtuf.coredump.cx/photo/current/