Date:	Mon, 30 Aug 1999 22:56:42 +0200
To:	pgcc AT delorie DOT com
Cc:	lauras AT softhome DOT net
Subject:	Re: PGCC 2.95.1 bug report
Message-ID:	<19990830225642.B27516@cerebro.laendle>
Mail-Followup-To:	pgcc AT delorie DOT com, lauras AT softhome DOT net
References:	<37C6E49A DOT B7DD966C AT softhome DOT net>
Mime-Version:	1.0
In-Reply-To:	<37C6E49A.B7DD966C@softhome.net>; from Laurynas Biveinis on Fri, Aug 27, 1999 at 09:18:50PM +0200
X-Operating-System:	Linux version 2.2.12 (root AT cerebro) (gcc driver version pgcc-2.95.1 19990816 (release) executing gcc version 2.7.2.3)
From:	Marc Lehmann <pcg AT goof DOT com>
Reply-To:	pgcc AT delorie DOT com
X-Mailing-List:	pgcc AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Fri, Aug 27, 1999 at 09:18:50PM +0200, Laurynas Biveinis <lauras AT softhome DOT net> wrote:
> This one bug report is from building libsocket for DJGPP -
> originally compilation of one file caused ICE, when I tried
> to track down error, ICE became endless-compilation, then SIGSEGV,
> then again ICE... So I attach preprocessed sources as they are.
> Even the same switches sometimes cause ICE, sometimes SIGSEGV,
> start using malloc-debugger for PGCC.

If you get different results using the same input data then its most
probably a hardware error (you might want to search the faq for "sig11" in
this case).

It might also be the case that djgpp still uses invalid asm statements in
its libc. I'll try to check for this in the attached source.

> I hope my report helps, bye.

Thanks or sending it in ;)


-- 
      -----==-                                             |
      ----==-- _                                           |
      ---==---(_)__  __ ____  __       Marc Lehmann      +--
      --==---/ / _ \/ // /\ \/ /       pcg AT goof DOT com      |e|
      -=====/_/_//_/\_,_/ /_/\_\       XX11-RIPE         --+
    The choice of a GNU generation                       |
                                                         |

- Raw text -