Mail Archives: djgpp/1999/09/10/00:52:06
Martin Stromberg wrote:
> Josh Reed (obitus AT uswest DOT net) wrote:
> : I have a program that I compiled with DJGPP that dies
> : half-way through execution. I used gdb on it and here is
> : what it said:
> : Program recieved signal SIGILL, Illegal instruction.
> : 0x1600 in scan (path=Cannot access memory at address
> : 0x2a2e2a64.) at audit.cpp:43
>
> : Line 43 in Audit.cpp:
> : if (((DTA.ff_attrib >= 16) && (DTA.ff_attrib <= 31)) ||
> : (DTA.ff_attrib >= 48))
>
> : Any help will be appreciated.
>
> : Josh
>
> : PS Tell me if you want me to post the whole function. It is
> : a recursive function that is suppose to find any file
> : matching the search string specified and display the
> : filename and path to the screen. Line 43 is testing whether
> : the file found is a directory that it can look in.
>
> "0x2a2e2a64" looks very much a part of a search expression. Translated to
> ASCII it's "*.*d". Looks familiar?
>
> It's likely that you overflowed your stack. This is of course just
> speculation.
>
> As for file finding, why not install findutils and use "find /some/dir
> -type f -iname 'd*' -print"?.
Well if I really wanted to find something I could use findutils or dir /s
for that matter. Its not finding something that I am worried about, it is
how can I write the code; how does that work? If somebody else has already
done it, that doesn't mean I can't, does it? Or did I miss something.
Josh
- Raw text -