Date: Wed, 4 Mar 1998 10:40:54 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Brian Sturk <bsturk AT nh DOT ultranet DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Allegro, spawnl, and PMODE/DJ...problems??
In-Reply-To: <34FCD658.666D2596@nh.ultranet.com>
Message-ID: <Pine.SUN.3.91.980304104033.6541O-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Tue, 3 Mar 1998, Brian Sturk wrote:

> Shutting down Allegro
> Exiting due to signal SIGILL
> Invalid Opcode at eip=00000008

EIP=00000008 is certainly a disaster!

>  // spawn process with the command line
>     int nRet;
>     nRet =  spawnl(P_WAIT, process_name, process_name, filename,
>                                         autorun_string, NULL);

Unless some of the string arguments to `spawnl' are set incorrectly, I
don't see anything wrong with this snippet.

Does the problem happen if you use CWSDPMI instead of PMODE/DJ?

> The full application (using Allegro's gui routines) called the
> spawnl the same way only preceded by allegro_exit().  The test app
> returned fine, and the one with Allegro returned with the above.

Can any Allegro guru help here?  I don't know enough about Allegro to
understand the implication of spawning a child program and calling
`allegro_exit' before that.