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
| ||
|
From: rodmur at maybe.org (Dale Harris) Subject: gcc: Internal compiler error: program cc1 got fatal signal 11 On Sat, Jan 10, 2004 at 12:41:20AM +0100, m.esco@...pl elucidated: > > No Segmentation Fault on Slackware 9.1, Kernel 2.4.24, GCC 3.2.3. > > > > Confimed - Segmentation Fault > > > > OS = Slackware 9.1.0 > > Kernel = 2.4.22 > > GCC = 3.2.3 > > > > int main(void) > > { > > printf("%c","msux"[0xcafebabe]); > > } > > $ gcc gcc-crash.c > > $ ./a.out > > Segmentation fault > > Well, honestly... is this interesting if seg. faults when you execute it? Or am I just missing something? You're accessing an array that hasn't been defined, that is a big "DUH!" in my book. It is interesting if it kills the compiler while trying to compile it, when it should be issuing a syntax error, not if the binary is executed. Hell, I have programs seg. fault all the time, no surprise there. Dale
Powered by blists - more mailing lists