gm2
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gm2] Bug Report


From: Gaius Mulley
Subject: Re: [Gm2] Bug Report
Date: Mon, 04 Apr 2011 16:06:52 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)

Alexandr Simon <address@hidden> writes:

> Hi, I try to compile the file and the compiler crashes
> with "Segmentation fault".
>
> 1. terminal $ uname -a
> Linux linux 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:34:50 UTC 2010 i686
> GNU/Linux
> ------------
> 2. nf.mod:
>
> MODULE Example;
> IMPORT Args, STextIO;
> BEGIN
>    STextIO.WriteString(Args);
> END nf.
> ------------
> 3. 
> terminal $ gm2 -v -save-temps nf.mod
> Using built-in specs.
> Target: i486-linux-gnu
> Configured with: ../gcc-4.1.2+gm2-20110223/configure --enable-languages=
> c,c++,gm2 --prefix=/opt/gm2 --libexecdir=/usr/lib/gm2/libexec --infodir=/opt/
> gm2/share/info --mandir=/opt/gm2/share/man --disable-nls --enable-long-long
> --without-included-gettext --with-dwarf2 --disable-libssp --disable-multilib
> --enable-libstdcxx-debug --enable-shared --build=i486-linux-gnu --host=
> i486-linux-gnu
> Thread model: posix
> gcc version 4.1.2
>  /usr/lib/gm2/libexec/gcc/i486-linux-gnu/4.1.2/cc1gm2 -quiet -dumpbase nf.mod
> -mtune=i486 -auxbase nf -version 
> -fobject-path=/opt/gm2/lib/gcc/i486-linux-gnu/
> 4.1.2/gm2/iso -ftarget-ranlib=/usr/bin/ranlib -ftarget-ar=/usr/bin/ar
> -fobject-path=/opt/gm2/lib/gcc/i486-linux-gnu/4.1.2/gm2/iso -ftarget-ranlib=/
> usr/bin/ranlib -ftarget-ar=/usr/bin/ar 
> -I/opt/gm2/lib/gcc/i486-linux-gnu/4.1.2/
> gm2/pim:/opt/gm2/lib/gcc/i486-linux-gnu/4.1.2/gm2/logitech:/opt/gm2/lib/gcc/
> i486-linux-gnu/4.1.2/gm2/iso -o nf.s nf.mod
> GNU Modula-2 version 4.1.2 (i486-linux-gnu)
> compiled by GNU C version 4.4.5.
> GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
> Internal error: Segmentation fault
> Please report this crash to the GNU Modula-2 mailing list <address@hidden>
>  ------------
> 4. Thank You for all of you work! ;)   

Hi,

many thanks for the bug report - yes the compiler should never sigsegv
even with weird input :-)

regards,
Gaius



reply via email to

[Prev in Thread] Current Thread [Next in Thread]