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>] [day] [month] [year] [list]

From: mr.pink at hushmail.com (mr.pink@...hmail.com)
Subject: gcc: Internal compiler error: program cc1 got fatal signal 11

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Fri, 09 Jan 2004 15:59:44 -0800 Dale Harris <rodmur@...be.org> wrote:

>
>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,

    It's legal, although undefined, C. However, when appropriate, the
compiler is allowed to issue a warning about accessing out of bounds
data. This assumes the array has been statically or automatically allocated.

    The reason the compiler is crashing when parsing the expression is
most likely a missing check determining whether (string literal + index)
lies within the symbol table. One thing I have noticed in a gcc version
that didn't crash, was that significantly large values for the index
caused code to be generated that calculates the resulting 'char' value
at runtime.

0x804831c <main+16>:    mov    $0xcafebabe,%eax
0x8048321 <main+21>:    mov    0x80483f4(%eax),%al

I would imagine gcc versions that crash do the above calculation at compile
time.

>not if the binary is executed.  Hell, I have
>programs seg.  fault all the time, no surprise there.
>
>
>Dale
>
-----BEGIN PGP SIGNATURE-----
Note: This signature can be verified at https://www.hushtools.com/verify
Version: Hush 2.3

wkYEARECAAYFAj//WP8ACgkQ00PjdRJ1pOcsfQCcD/+k1C3/A8xZ6dlVS5i0I92+PowA
n3QNAabLL5TxIQAjcS8TqkIzmAHl
=EtXB
-----END PGP SIGNATURE-----




Concerned about your privacy? Follow this link to get
FREE encrypted email: https://www.hushmail.com/?l=2

Free, ultra-private instant messaging with Hush Messenger
https://www.hushmail.com/services.php?subloc=messenger&l=434

Promote security and make money with the Hushmail Affiliate Program: 
https://www.hushmail.com/about.php?subloc=affiliate&l=427