From:	anorland AT hem2 DOT passagen DOT se (Anders Norlander)
Subject:	Re: bug with gcc with findfirst/findnext
7 Nov 1998 04:05:48 -0800 :
Message-ID:	<36422009.34D9DCF8.cygnus.gnu-win32@hem2.passagen.se>
References:	<m0zar9b-0002i9C AT jacob DOT remcomp DOT fr>
Mime-Version:	1.0
To:	root <root AT jacob DOT remcomp DOT fr>
Cc:	gnu-win32 AT cygnus DOT com

root wrote:
> 
> The functions
> _findfirst
> and
> _findnext
> Will not work with the last version of gcc (mingw32).
[snip]
> It will list only the first file and then STOP!!!
> _findnext returns inexplicably -1!!!!
> 
> I have discovered this problem with egcs because... lcc-win32 has the SAME
> problem. With exactly the same symptoms.
> 
> What is REALLY WEIRD is that if you run the same executable that fails under
> the msvc debugger, it will work!!!
> 
> If you run the same executable that fails under wedit, lcc-win32's debugger,
> it will work too!
> 
> If you compile with gcc, gdb will NOT make that work, probably because it is
> a console mode debugger.
> 
> If you use *the same code* in a windows program, it will work. The problem
> appears only in console applications.
> 
> Have any of you any clues to what the hell is going on there?

The wildcards on the command line arguments are expanded so only
the first file (in argv[1]) will be listed. I don't know why they
are not expanded in the debugger though.

Anders Norlander
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -