This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: bug with gcc with findfirst/findnext
- To: root <root at jacob dot remcomp dot fr>
- Subject: Re: bug with gcc with findfirst/findnext
- From: Anders Norlander <anorland at hem2 dot passagen dot se>
- Date: Thu, 05 Nov 1998 23:00:41 +0100
- CC: gnu-win32 at cygnus dot com
- References: <m0zar9b-0002i9C@jacob.remcomp.fr>
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@cygnus.com" with one line of text: "help".