Date: Tue, 25 Sep 2001 08:57:35 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Thomas Hutto <huttothomas AT hotmail DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: A perplexing runtime anomoly
In-Reply-To: <F160CTaogxLDp7mvjkO00004e15@hotmail.com>
Message-ID: <Pine.SUN.3.91.1010925085608.11596C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 24 Sep 2001, Thomas Hutto wrote:

> Running Windows ME on AMD Athlon 1.1GHz w/ 512 MRAM
> Disk space to burn.
> 
> I've never seen this one before, maybe someone else has.
> 
> The makefile is included below.
> 
> I can compile and successfully run the associated *.c files using a nameless 
> commericial complier/ide.
> 
> However when I use the following makefile with DJGPP I get an bridge.exe 
> file that does NOTHING. And I do mean nothing, no lockup, no crash, no error 
> messages and no version message from the pgm
> 
> The first executable statement is a printf giving program name and version 
> number.

I'd suggest to compile with -gstabs+ and run the program under a 
debugger.  Put a breakpoint at the entry into `main' and at the `exit' 
and `_exit' functions, and see what happens.