Date: Wed, 20 May 1998 12:29:48 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Anonymous <nobody AT REPLAY DOT COM>
cc: djgpp AT delorie DOT com
Subject: Re: Execution finished before started!
In-Reply-To: <199805191341.PAA15048@basement.replay.com>
Message-ID: <Pine.SUN.3.91.980520122930.24974S-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Tue, 19 May 1998, Anonymous wrote:

> Load failed for image \obj/myprog.exe

This shouldn't happen.  You should try to understand why did GDB fail
to load the program.  It works for me.

> 'symify' reveals nothing but the command itself in the output file
> (assuming a clear screen).

I don't understand.  What's that ``clear screen'' business about?  Did
you try to run `symify' when no crash traceback is displayed on the
screen?  If so, it indeed won't work, since it doesn't have anything
to symify.

> Clearly there is something bad happening between the startup code
> and the malloc (wrapper?) functions in the malloc debugging library.
> I can't imagine how they could prevent a simple startup.

The startup code is mostly C, and it itself calls malloc.  If there's
some bug or incompatibility with DJGPP in the replacement malloc, the
startup will crash.

Please post the symified crash traceback here.  Please make sure you
compile your program with -g, so that `symify' will have symbols to
report.  Also, please run your program from the command line, not from
RHIDE, when you are generating the traceback.