Re: seg fault ~30G

2007-12-26 Thread Micah Cowan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Steven M. Schweda wrote:
 From: Hunter
 
 I'm getting a seg fault anytime I approach 30G in transfer with wget.

 I did a google search, but didn't see a resolution.  Is there one I
 simply cannot find?
 
It's hard to say.  I'll tell you what I can't find here, and that's a
 useful problem report, which would include things like the wget version
 (wget -V), the OS you're using and its version, and the actual wget
 command you used (and its output).  As usual, adding -d to the command
 might be informative.  In a case where the program explodes, a traceback
 showing where it was when it died could also be helpful.  (Not knowing
 your OS makes it hard to suggest how to get a traceback.)  Evidence that
 you have adequate free disk space could be reassuring, too.
 
There isn't anything magic about 30G (as there is about, say, 2G or
 4G), so I'd guess that it'd more likely be a problem in your environment
 than in wget, but with the available evidence, that is only a guess.

Even with 2G or 4G, I'd consider SIGXFSZ (exceeded maximum file size,
dumps core) more likely than SIGSEGV. Even as it is, I'd like to rule
that (and other core-dumping signals) out. Hunter, you're sure it was a
seg fault (that is, you're not just assuming it was a seg fault because
core was dumped)?

The diagnostics that Steven has suggested (specifying the wget version,
using -d, obtaining a traceback) would be extremely helpful. In fact,
there's really not much we could do without the stack trace (with
debugging symbols active); unless we can find a case we can reproduce on
our end.

If you're not using the bleeding-edge code, it'd be helpful to know
whether you still experience problems with the development version of
Wget: http://wget.addictivecode.org/RepositoryAccess to get the source
code, or if you're on Windows, get it from
http://www.christopherlewis.com/WGet/WGetFiles.htm.

- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
http://micah.cowan.name/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHcpwC7M8hyUobTrERAo9XAJ42+msWEAhkrnqEayCwsBj3f9jHYwCeMri4
i11TGtN2w1o+nw1pClHzAJ4=
=Jp+K
-END PGP SIGNATURE-


seg fault ~30G

2007-12-24 Thread Hunter
I'm getting a seg fault anytime I approach 30G in transfer with wget.

I did a google search, but didn't see a resolution.  Is there one I simply
cannot find?

_hunter


Re: seg fault ~30G

2007-12-24 Thread Steven M. Schweda
From: Hunter

 I'm getting a seg fault anytime I approach 30G in transfer with wget.
 
 I did a google search, but didn't see a resolution.  Is there one I
 simply cannot find?

   It's hard to say.  I'll tell you what I can't find here, and that's a
useful problem report, which would include things like the wget version
(wget -V), the OS you're using and its version, and the actual wget
command you used (and its output).  As usual, adding -d to the command
might be informative.  In a case where the program explodes, a traceback
showing where it was when it died could also be helpful.  (Not knowing
your OS makes it hard to suggest how to get a traceback.)  Evidence that
you have adequate free disk space could be reassuring, too.

   There isn't anything magic about 30G (as there is about, say, 2G or
4G), so I'd guess that it'd more likely be a problem in your environment
than in wget, but with the available evidence, that is only a guess.



   Steven M. Schweda   [EMAIL PROTECTED]
   382 South Warwick Street(+1) 651-699-9818
   Saint Paul  MN  55105-2547