Mail Archives: djgpp/1999/08/21/13:15:48
On 20 Aug 99, at 17:23, Endlisnis wrote:
> salvador wrote:
>
> > > 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
>
> OK, I figured out what was causing the problem. It was the HOME environmental variable.
> For some reason, when RHIDE loads with the HOME environmental variable set to the root directory
> of any drive, it waits 120 seconds before loading, but only if DJDIR is set. I had my DJGPP
> installed in a subst'ed drive, and my HOME was set to "P:\", but when i changed it to the real
> location "E:\DJGPP\", rhide loads fine.
> Thanx for your assistance.
>
I'ts bug in rhide. RHIDE tries to to open something like c:\/rhide.env
what places Wincrash9X to sleep for about 5 seconds (rhide looks for
files many times, so the delay is bigger)
Tried to hack sources in librhuti but didn't suceed quickly. So I left it
as it is
Andris
PS. Second identical bug this week. First were in collect2 (gcc295X.zip)
- Raw text -