From:	Shawn Rusaw <wasurs AT cs DOT sfu DOT ca>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Program does not run correctly after SIGINT
Date:	Mon, 30 Mar 1998 13:37:06 -0800
Organization:	Simon Fraser University
Lines:	38
Message-ID:	<35201082.7297@cs.sfu.canada>
NNTP-Posting-Host:	russell.ensc.sfu.ca
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

I recently decided DJGPP for its easy access to extended
memory. My app's port from BCC was very easy (just removed references 
to huge pointers), but my app's behaviour is another matter.

Since there is no small amount of representative code that
demonstrates the problem I will simply describe the behaviour.

1. Hard Boot computer
2. Run program - the program collects data
3. midway through collecting data, I press <ctrl><c> or <ctrl><brk>
   which delivers a SIGINT, stopping the program.
4. If I try to run the program again, It seems to startup using
   some of the data from the previous run.

This sort of thing has never happened before (using BCC or using
gcc in a Solaris environment). My gut feeling is the stack is
somehow getting munged, but really don't have a firm grasp what
to do.

Do I need to handle the SIGINT?  Is it done behind the scenes with
other compilers? (i've used gcc before, and never seen this)

OTHER INFO:

copiled with command line
gcc -g -x c++ -c filename.c -o filename.o

linked with command line
gcc -x c++ -o filename.exe filename.o -lbcc2 -lgrx20 -lstdcx

Other posts have metioned stack problems and I cannot find anything 
in FAQ2.10.

----------------------------
Shawn Rusaw (instead of 'canada', use the country code 'ca'
	     in my email address to respond)
Experimental Robotics Laboratory              
Simon Fraser University

- Raw text -