delorie.com/archives/browse.cgi | search |
Xref: | news-dnh.mv.net comp.os.msdos.djgpp:2415 |
Path: | news-dnh.mv.net!mv!news.sprintlink.net!in1.uu.net!noc.near.net!das-news2.harvard.edu!oitnews.harvard.edu!news.sesqui.net!rice!news!sandmann |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Stupped : V2.0 bug? |
Date: | Tue, 03 Oct 1995 15:46:30 CDT |
Organization: | Rice University, Houston, Texas |
Lines: | 11 |
References: | <44qj8a$boi AT sisko DOT dnaco DOT net> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
Nntp-Posting-Host: | clio.rice.edu |
To: | djgpp AT sun DOT soe DOT clarkson DOT edu |
Dj-Gateway: | from newsgroup comp.os.msdos.djgpp |
> under 1.12.4 run's w/o error > under 2.0 gets a nasty SEGFAULT while accessing a 2d array of floats. It's difficult to say what the problem is without a complete listing of the source assembly line causing the fault and the contents of all the registers. But in almost all cases I have seen so far, V2 execution failures have been related to programs expecting uninitialized memory (stack/malloc) values to be set to zero when first accessed, which V2 no longer does (unless you include crt0.h and set a special flag to zero the memory).
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |