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]

Message-ID: <3FFDB73C.4030600@snosoft.com>
From: dotslash at snosoft.com (KF)
Subject: gcc: Internal compiler error: program cc1 got
 fatal signal 11

I don't believe there is a need to show the resulting binary 
segfaulting... if gcc does not seg during the compile then its not vuln. 
Running the a.out I would imagine segfaults everywhere.

-KF

> $ gcc gcc-crash.c
> $ ./a.out
> Segmentation fault