RE: Bug in GNU Wget 1.x (Win32)
> From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Þröstur > Sent: Wednesday, June 21, 2006 4:35 PM There have been some reports in the past but I don't think it has been acted upon; one of the problems is that the list of names can be extended at will (beside the standard comx, lptx, con, prn). Maybe it is possible to query the os about the currently active device names and rename the output files if neccessary ? > I reproduced the bug with Win32 versions 1.5.dontremeber, > 1.10.1 and 1.10.2. I did also test version 1.6 on Linux but it > was not affected. That is since the problem is generated by the dos/windows filesystem drivers (or whatever those should be called), basically com1* and so on are equivalent of unix device drivers, with the unfortunate difference of acting in every directory. > > Example URLs that reproduce the bug : > wget g/nul > wget http://www.gnu.org/nul > wget http://www.gnu.org/nul.html > wget -o loop.end "http://www.gnu.org/nul.html"; > > I know that the bug is associated with words which are > devices in the windows console, but i don't understand > why, since I tried to set the output file to something else. I think you meant to use -O, not -o. Doesn't solve the real problem but at least a workaround. Heiko -- -- PREVINET S.p.A. www.previnet.it -- Heiko Herold [EMAIL PROTECTED] [EMAIL PROTECTED] -- +39-041-5907073 / +39-041-5917073 ph -- +39-041-5907472 / +39-041-5917472 fax
Bug in GNU Wget 1.x (Win32)
Hello there, I have to say that Wget is one of the most useful tools out there(from my point of view of course). I'm using the Win32 version of it to make life with XP little more bearable. (faking Internet Explorer like mad, all over the place) Well on to the thing i call a bug. The bug only affects the Win32 version. It seems that when a file name(not the extension) in an URL is either nul, con, com1 and so on Wget goes into an endless loop(did not wait that long though). I reproduced the bug with Win32 versions 1.5.dontremeber, 1.10.1 and 1.10.2. I did also test version 1.6 on Linux but it was not affected. Example URLs that reproduce the bug : wget g/nul wget http://www.gnu.org/nul wget http://www.gnu.org/nul.html wget -o loop.end "http://www.gnu.org/nul.html"; I know that the bug is associated with words which are devices in the windows console, but i don't understand why, since I tried to set the output file to something else. But then again i did not look at the source code so i only have my self to blame. This could be a known problem, or it will not be fixed because Wget is native to Linux, but i thought you guys should at least notified about this. Best regards, Throstur S. Eidsson. p.s. I already sent this e-mail before but i think i ran into trouble with your e-mail confirmation. So here goes take two.
Bug in GNU Wget 1.x (Win32)
Hello there, I have to say that Wget is one of the most useful tools out there(from my point of view of course). I'm using the Win32 version of it to make life with XP little more bearable. (faking Internet Explorer like mad, all over the place) Well on to the thing i call a bug. The bug only affects the Win32 version. It seems that when a file name(not the extension) in an URL is either nul, con, com1 and so on Wget goes into an endless loop(did not wait that long though). I reproduced the bug with Win32 versions 1.5.dontremeber, 1.10.1 and 1.10.2. I did also test version 1.6 on Linux but it was not affected. Example URLs that reproduce the bug : wget g/nul wget http://www.gnu.org/nul wget http://www.gnu.org/nul.html wget -o loop.end "http://www.gnu.org/nul.html"; I know that the bug is associated with words which are devices in the windows console, but i don't understand why, since I tried to set the output file to something else. But then again i did not look at the source code so i only have my self to blame. This could be a known problem, or it will not be fixed because Wget is native to Linux, but i thought you guys should at least notified about this. Best regards, Throstur S. Eidsson.
