full-disclosure - gcc: Internal compiler error: program cc1 g ot 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-next>] [day] [month] [year] [list]

Message-ID: <9B66BBD37D5DD411B8CE00508B69700F05ADDAE9@pborolocal.rnib.org.uk>
From: John.Airey at rnib.org.uk (John.Airey@...b.org.uk)
Subject: gcc: Internal compiler error: program cc1 g
	ot fatal signal 11 

> -----Original Message-----
> From: Kurt Schreiner [mailto:ks@...uni-mainz.de]
> Sent: 09 January 2004 08:43
> To: Valdis.Kletnieks@...edu
> Cc: guninski@...inski.com; full-disclosure@...ts.netsys.com
> Subject: Re: [Full-Disclosure] gcc: Internal compiler error: 
> program cc1
> got fatal signal 11 
> 
> 
> 
> Hi,
> 
> > 3) This is why it *will* segfault at runtime.  If it 
> *fails* to segfault at runtime,
> > you have a *very* weird system indeed (or possibly very 
> weird compiler flags ;)
> 
> just tried this on solaris9/sparc:
> >-349: uname -a
> SunOS sb1001 5.9 Generic_112233-05 sun4u sparc SUNW,Sun-Blade-1000
> 
> using:
> >-333: gcc -v
> Reading specs from 
> /opt/nb/gcc-3.3/lib/gcc-lib/sparc-sun-solaris2/3.3/specs
> Configured with: ./configure --prefix=/opt/nb/gcc-3.3 
> --host=sparc-sun-solaris2 
> --enable-languages=c,c++,f77,objc,ada --enable-shared
> Thread model: posix
> gcc version 3.3
> 
> >-339: cat gcc-muell.c 
> int main(void)
> {
>  printf("%c","msux"[0xcafebabe]);
> }
> 
> >-340: gcc gcc-muell.c 
> [Compiles w/o compaints!]

Guys, this is getting to be a peeing contest. Can anyone confirm that the
gcc maintainers are aware of this, and are they able to make a statement as
to which compilers need their optimisation code sorted?

I mean, if we did this kind of gross dissection of every bug, we'd be
deleting messages all day and not doing any work. Full-disclosure doesn't
mean full-boredom!

To be specific:

1. Feel free to report a bug
2. Wait for a fix or provide one yourself.
3. Go back to 1 if 2 doesn't fix it.

Thank you.

- 
John Airey, BSc (Jt Hons), CNA, RHCE
Internet systems support officer, ITCSD, Royal National Institute of the
Blind,
Bakewell Road, Peterborough PE2 6XU,
Tel.: +44 (0) 1733 375299 Fax: +44 (0) 1733 370848 John.Airey@...b.org.uk 

Even if you win the rat race, that will still only make you a rat.

- 
DISCLAIMER: 

NOTICE: The information contained in this email and any attachments is 
confidential and may be privileged. If you are not the intended 
recipient you should not use, disclose, distribute or copy any of the 
content of it or of any attachment; you are requested to notify the 
sender immediately of your receipt of the email and then to delete it 
and any attachments from your system. 

RNIB endeavours to ensure that emails and any attachments generated by 
its staff are free from viruses or other contaminants. However, it 
cannot accept any responsibility for any  such which are transmitted.
We therefore recommend you scan all attachments. 

Please note that the statements and views expressed in this email and 
any attachments are those of the author and do not necessarily represent 
those of RNIB. 

RNIB Registered Charity Number: 226227 

Website: http://www.rnib.org.uk