Date:	Tue, 23 Jan 2001 12:15:27 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	florianx <florianx AT drdos DOT org>
cc:	djgpp AT delorie DOT com
Subject:	Re: silly question: SIGSEGV
In-Reply-To:	<3a6c9209$0$12666@SSP1NO25.highway.telekom.at>
Message-ID:	<Pine.SUN.3.91.1010123121510.9288E-100000@is>
MIME-Version:	1.0
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

On Mon, 22 Jan 2001, florianx wrote:

> >>   0xffd94c14 0xffd94c14   <------------- funtktion in the DLX program
> >>   0x00003d23 _dispose+31, line 1476 of program.c
> >
> >This *may* be part of your problem. Note that dispose() is being
> >called recursively, with only that slightly volatile 'DLX program' in
> >between. Iff that routine uses any kind of non-volatile storage in a
> >way DLX doesn't expect, this could get you in trouble.
> 
> The Program is a GUI, first it shut down all subviews, then the view, so it
> must be recursively. :(

What Hans-Bernhard was trying to tell you is that recursive
invocations require cautious coding, to make sure you don't use
non-reentrant code or data.

> >1) use -gstabs+ or -ggdb instead of -g in GCC
> 
> Thx. I will also try -ggdb
> 
> Does somebody know, what I can use for DLX instead of -gstabs+? It doesn't
> go (DLX files cannot be loaded).

Does it work to compile only non-DLX parts with -gstabs+?

- Raw text -