delorie.com/archives/browse.cgi | search |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: ok under GDB crash under msdos ?? |
Date: | Wed, 24 Jul 2002 11:18:00 CDT |
Organization: | Rice University, Houston TX |
Lines: | 8 |
Message-ID: | <3d3ed338.sandmann@clio.rice.edu> |
References: | <ahm6uj$sbt47$1 AT ID-106847 DOT news DOT dfncis DOT de> |
NNTP-Posting-Host: | clio.rice.edu |
X-Trace: | joe.rice.edu 1027527482 7115 128.42.105.3 (24 Jul 2002 16:18:02 GMT) |
X-Complaints-To: | abuse AT rice DOT edu |
NNTP-Posting-Date: | 24 Jul 2002 16:18:02 GMT |
X-NewsEditor: | ED-1.5.9 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
> I have some code that runs fine when it's executed under GDB, but when I try > it standalone it GPF's. Can anyone suggest how to find the error? 1) Symify - it tells you where it crashed; from the contents of the registers listed and a little disassembly of that instruction, you can see which variable had contents causing the problem. 2) Set the crt0 flag to zero all memory - if that helps it's an uninitialized variable issue.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |