Sender: root AT delorie DOT com
Message-ID: <37B98062.A17BA5C5@inti.gov.ar>
Date: Tue, 17 Aug 1999 12:31:47 -0300
From: salvador <salvador AT inti DOT gov DOT ar>
Organization: INTI
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: es-AR, en, es
MIME-Version: 1.0
To: djgpp AT delorie DOT com
CC: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, Endlisnis <s257m AT unb DOT ca>
Subject: Re: RHIDE crashes without traceback.
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990815104524 DOT 1935B-100000 AT is> <37B77A79 DOT FA93DE01 AT unb DOT ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Endlisnis wrote:

> Eli Zaretskii wrote:
>
> > On Thu, 12 Aug 1999, Endlisnis wrote:
> >
> > >     It turns out that it has nothing to do with the DJGPP variable, but the DJDIR
> > > variable.  If I point DJGPP to a non-existant file, RHIDE does not crash, but it is
> > > not djgpp.env that is crashing rhide.exe.  I know this because if I unset DJGPP,
> > > and then manually set DJDIR to point to ANYTHING (valid or not), it crashes
> > > immediately when I run it.
> >
> > It seems that it crashes somewhere in the startup code (that's the place
> > where the DJDIR variable is processed by looking up and loading
> > djgpp.env).  I think it would help to find out where exactly does it
> > crash.  The best way to do that would be to run RHIDE under a debugger
> > such as GDB or FSDB and single-step the program until it hangs.  Then
> > post here the instruction where it crashed and a couple of dozens of
> > instructions from its vicinity.
> >
> > But first make sure the bug at all exists when you run RHIDE under a
> > debugger.
>
>     OK, I've discovered that it doesn't actually "crash", it just get's hung for ~2
> minutes when trying to do something with DJDIR.  Running it in gdb doesn't change
> anything.  Using exe2coff/go32-v2 doesn't change anything.  If I wait 2 minutes, it loads
> and runs normally.  During the 2 minute wait, it does not respond to ^C/^Break.
> (Remember, it still loads normally under DOS)

Check your TEMP, TMPDIR and TMP definitions! (including the definition found in djgpp.env)
most probably one of them is pointing to an invalid drive (or non-existant directory). RHIDE
and CVS will wait for a long time before giving up (is libc). I added a lot of checks in the
editor code to avoid such a problem.
RHIDE uses DJDIR as part of the TMP guess so it could be the reason.

SET

--
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Visit my home page: http://welcome.to/SetSoft or
http://www.geocities.com/SiliconValley/Vista/6552/
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
                    set AT ieee DOT org set-soft AT bigfoot DOT com
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013