Compiler segfault under fbsd7?

[cy at htlwrn.ac.at]

   You are right: make buildworld exits with

    
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/genattrtab.c:  
In function 'make_internal_attr':
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/genattrtab.c:4240:  
internal compiler error: Segmentation fault: 11

   So it's some hardware than (could it be an old BIOS).

   Or could it be the HD, fdisk gives:

   ******* Working on device /dev/ad0 *******
parameters extracted from in-core disklabel are:
cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 63, size 156296322 (76316 Meg), flag 80 (active)
        beg: cyl 0/ head 1/ sector 1;
        end: cyl 1023/ head 254/ sector 63

   I tried to fix this with fdisk to the correct 1024/255/63 but the  
upper part of the output stays always the same ...

   Thx

   Werner

   Quoting Jeremy Chadwick <koitsu at FreeBSD.org>:

> On Tue, May 27, 2008 at 10:57:03AM +0200, cy at htlwrn.ac.at wrote:
>>    Hi I just tried to install the apache22 port - ended in a
>>    segmentation fault in port (=dependency) phyton:
>>
>>    ./../Objects/unicodeobject.c: In function
>> 'unicode_decode_call_errorhandler':
>> ./../Objects/unicodeobject.c:874: internal compiler error: Segmentation
>> fault: 11
>> Please submit a full bug report,
>> with preprocessed source if appropriate.
>> See <URL:http://gcc.gnu.org/bugs.html[1]> for instructions.
>> *** Error code 1
>>
>>    Stop in /usr/ports/lang/python25/work/Python-2.5.2/portbld.static.
>> *** Error code 1
>> Its a brand new install of BSD 7 and its the first port I tried to install
>> after portsnap fetch and portsnap extract - so what could possibly be
>> wrong??
>
> This is covered in the FAQ.  In most cases, it's a sign of hardware
> problems (usually bad memory).
>
> http://www.freebsd.org/doc/en/books/faq/troubleshoot.html#SIGNAL11
>
> Can you complete an entire buildworld (cd /usr/src && make buildworld)
> without sig11?  If so, it may in fact be a compiler bug, but I'm
> doubting it.
>
> --
> | Jeremy Chadwick                                jdc at parodius.com |
> | Parodius Networking                       http://www.parodius.com/ |
> | UNIX Systems Administrator                  Mountain View, CA, USA |
> | Making life hard for others since 1977.              PGP: 4BD6C0CB |
>
>

*****************************************************************************
Mag. Werner Cyrmon
HTBLuVA Wr. Neustadt, Abt. EDVO
Change is Life!(Remi, Ratatouille)
*****************************************************************************
NOTICE: This message and any attachment are confidential.
If you are not the intended recipient, please notify the sender and delete
this e-mail and any copies.
Incoming e-mails are not accepted as legally binding unless legal validity is
confirmed by us by reply-mail.
An automatically generated acknowledgement of receipt cannot be considered as
confirmation of legal validity.

---------------------------------------------------------------------
This message was sent using the HTL Wr. Neustadt/EDVO webmail service.