OpenEuphoria

Re: machine level exception in file.e again

• Posted by Kat <KAT12 at coosahs??et> May 16, 2008
• 643 views

Matt Lewis wrote:
> 
> Kat wrote:
> >  
> > > <a
> > > href="http://www.rapideuphoria.com/win_dir.zip">http://www.rapideuphoria.com/win_dir.zip</a>
> > > 
> > 
> > I have it, it seems to be a program to munge normal dir output. Munging such
> > data cannot be the problem if dir never returns. I asked if i can trap the
> > non-returning
> > dir, called in file.e, in the machine call, and been told no, so i don't see
> > why another lib of eu code could.
> 
> Yeah, this is basically what I was thinking:  the c-library routine for
> dir choked on the big file size.  Which is why I asked about that file.

What big file? Dir() is seeing only a lot of ~100K files, i don't think but a
few are 2 megabytes or so, and many are under 1k bytes.

> You could build a debug version of euphoria, and use the watcom debugger to
> step through.  This won't go into the internals of the c-library, though.

I keep asking where watcom is, why when i look for it that it's not sold or
supported anymore, and i never get a source for it, so i don't have it. Not in
all the time i have been using Euphoria. Besides, i'd need it to run full speed
til there's an abnormality, and since there are legitimate -1 returned, sitting
here for day after day watching it ask me "is this ok?", "is this ok?" every few
minutes would just be too much. I believe Jeremy is now compiling eu v4.0 on
openwatcom, which isn't the same beast as watcom.

> I was talking about the munging going on to prepare the data returned by dir.
> Since Greg's library uses Win32 calls, I thought it might avoid a potential
> problem with the watcom runtime library.

That's a possibility, yeas. Doesn't dir() use such win32 calls? Does it use bios
calls?
 
> I promise not to try to be helpful on this thread anymore.

I think our emails are crossing, and this conversation is desync'd. I appreciate
your help, but atm i think we don't have a clue what the other is talking about.
I know i am confused why people think i keep running dir() with a huge file in
the dir, and thinking it's the problem, and why i don't move it to another dir,
when in fact it's been in other dirs and different drives all this time.

Kat