bugGNU Wget - Bugs: bug #47425, crash on download on specific...

 
 

bug #47425: crash on download on specific hardware (Dell Dimension 2400)

Submitted by:  Shawn <shawnkhall>
Submitted on:  Wed 16 Mar 2016 09:34:37 AM UTC  
 
Category: Crash/Freeze/InfloopSeverity: 3 - Normal
Priority: 5 - NormalStatus: None
Privacy: PublicAssigned to: None
Originator Name: Open/Closed: Closed
Release: 1.17.1Operating System: Microsoft Windows
Reproducibility: Every TimeFixed Release: None
Planned Release: NoneRegression: None
Work Required: NonePatch Included: None

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Wed 16 Mar 2016 12:13:19 PM UTC, comment #2:

Maybe a similar problem as
https://savannah.gnu.org/bugs/?46943

Tim Ruehsen <rockdaboot>
Project Administrator
Wed 16 Mar 2016 12:09:51 PM UTC, comment #1:

This sounds like your version of Wget contains assembler code that your old P4s doesn't know. Try to compile a version on your P4 machines, or just stay with a working executable !?

Tim Ruehsen <rockdaboot>
Project Administrator
Wed 16 Mar 2016 09:34:37 AM UTC, original submission:

I'll be testing more thoroughly tomorrow, but here's what I know so far. I have three separate Dell Dimension 2400 machines running Windows 7 Home Premium and Wget 1.17.1. I have hundreds of other computers I work on. These three consistently crash Wget with the following error:

-----
Source: Application Error
EventID: 1000
Task Category: (100)

Faulting application name: wget.exe, version: 0.0.0.0, time stamp: 0x41797261
Faulting module name: wget.exe, version: 0.0.0.0, time stamp: 0x41797261
Exception code: 0xc000001d
Fault offset: 0x0022cffa
Faulting process id: 0xf60
Faulting application start time: 0x01d17e332882035d
Faulting application path: c:\Tools\wget.exe
Faulting module path: c:\Tools\wget.exe
Report Id: 695bb73f-ea26-11e5-8a4a-000f1f56cea3

Faulting application name: wget.exe, version: 0.0.0.0, time stamp: 0x41797261
Faulting module name: wget.exe, version: 0.0.0.0, time stamp: 0x41797261
Exception code: 0xc000001d
Fault offset: 0x0022cffa
Faulting process id: 0x760
Faulting application start time: 0x01d17e22a875e7ab
Faulting application path: c:\Tools\wget.exe
Faulting module path: c:\Tools\wget.exe
Report Id: e7f65904-ea15-11e5-a89a-000f1f56cea3

Faulting application name: wget.exe, version: 0.0.0.0, time stamp: 0x41797261
Faulting module name: wget.exe, version: 0.0.0.0, time stamp: 0x41797261
Exception code: 0xc000001d
Fault offset: 0x0022cffa
Faulting process id: 0x440
Faulting application start time: 0x01d17dc7c2a6b848
Faulting application path: c:\Tools\wget.exe
Faulting module path: c:\Tools\wget.exe
Report Id: 02885174-e9bb-11e5-a89a-000f1f56cea3

Source: Application Error
EventID: 1005
Task Category: (100)

Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program wget.exe because of this error.

Program: wget.exe
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0

-----

One of the first errors (1000) will appear in the event log with the last error (1005) EVERY time I run this version of Wget on this hardware. If I revert to an older version (1.16) it works fine.

I've performed exhaustive hardware troubleshooting (spinrite, sfc, chkdsk, memtest86, dell diag) and they each return okay. The machines are each running 2GB RAM on P4 2.8GHz CPUs. They're horribly slow, but I have other computers from the same generation that are still using Wget okay, even on XP and Vista.

Shawn <shawnkhall>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by darnir (Updated the item)
  • -unavailable- added by rockdaboot (Posted a comment)
  • -unavailable- added by shawnkhall (Submitted the item)
  • -unavailable- added by shawnkhall
  •  

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 2 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Thu 26 May 2016 02:02:59 PM UTCdarnirOpen/ClosedOpen=>Closed
    Wed 16 Mar 2016 09:34:38 AM UTCshawnkhallCarbon-Copy-=>Added shawnkhall

    Back to the top


    Powered by Savane 3.1-cleanup1