aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: CVS 20051008 Crashes on finding a large file?  (Read 2849 times)

vdb

  • Full Member
  • ***
  • Karma: 1
  • Offline Offline
  • Posts: 215
CVS 20051008 Crashes on finding a large file?
« on: October 09, 2005, 11:51:23 AM »

I have compiled amule 20051008 yesterday and now it seemed to crash if I use my standard shareddir file. Some investigating led me to one particular file of 3.8 GB size. When I moved this one out, the monolithic and daemon version started like normal.

This has never occured before with the 2.0.3 version. Perhaps it is the wxGTK which I upgraded from 2.4.2 to 2.6.1? Does that have a problem with large files, even if it states that this is supported (see backtrace).

Any thoughts on this?

Backtraces are posted in the backtrace thread.
« Last Edit: October 09, 2005, 11:51:39 AM by vdb »
Logged
A waste is a terrible thing to mind.

Vollstrecker

  • Administrator
  • Hero Member
  • *****
  • Karma: 67
  • Offline Offline
  • Posts: 1546
  • Unofficial Debian Packager
    • http://vollstreckernet.de
Re: CVS 20051008 Crashes on finding a large file?
« Reply #1 on: October 09, 2005, 12:36:01 PM »

Maybe your fs doesn't support that large files.
Logged
Homefucking is killing prostitution

vdb

  • Full Member
  • ***
  • Karma: 1
  • Offline Offline
  • Posts: 215
Re: CVS 20051008 Crashes on finding a large file?
« Reply #2 on: October 09, 2005, 01:41:15 PM »

Nope, can't be it, since 2.0.3 has shared this file without a problem for a few months. And now that I reverted back to 2.0.3 it is shared again, no crash in sight.
Logged
A waste is a terrible thing to mind.

vdb

  • Full Member
  • ***
  • Karma: 1
  • Offline Offline
  • Posts: 215
Re: CVS 20051008 Crashes on finding a large file?
« Reply #3 on: October 09, 2005, 04:40:57 PM »

And one more interesting feature on this thread: I recompiled amule 2.0.3 using the same wxGTK-2.6.1 libraries I used to create the CVS. And now suddenly I get an error message, but it does not crash the monolith:

2005-10-09 16:50:33: CFile: Error in lseek: Invalid argument
2005-10-09 16:50:33: AICH Thread: Syncronization thread started.
2005-10-09 16:50:33: CFile: Can't find length of file '/opt/shares/films//WhateverBigFile.rar' with file descriptor '14'.
2005-10-09 16:50:33: Hasher: Warning, file is bigger than 4GB, skipping: /opt/shares/films//WhateverBigFile.rar
2005-10-09 16:50:33: Hasher: No files on queue, stopping thread.
2005-10-09 16:50:33: Hasher: A thread has died.

Filesize is actually NOT bigger then 4 GB:
-rw-r-----  1 xx yy 3,877,534,083 Sep 30 23:30 WhateverBigFile.rar

So, it seems that the crash on the CVS is linked to the wxGTK version. But in 2.0.3 it does not actually crash the application, in CVS 20051008 it does.

Any thoughts?

[Edit - I removed AGAIN your references to copyrighted material. Next time you're banned. you're warned]
Logged
A waste is a terrible thing to mind.

vdb

  • Full Member
  • ***
  • Karma: 1
  • Offline Offline
  • Posts: 215
Re: CVS 20051008 Crashes on finding a large file?
« Reply #4 on: October 09, 2005, 06:30:47 PM »

And one last addition to this post: When installing a 2.0.3 version from the RPM's as provided by the linfreak ftp site, linked against the wxGTK 2.6.0 libraries, it does run past the large file error without crashing.

All this leads me to believe that there is a bug in the CVS code, not in the wxGTK.

Can one of the coders take a look at that?

Thanks
Logged
A waste is a terrible thing to mind.

vdb

  • Full Member
  • ***
  • Karma: 1
  • Offline Offline
  • Posts: 215
Re: CVS 20051008 Crashes on finding a large file?
« Reply #5 on: October 15, 2005, 01:05:45 PM »

One more addition to this thread: Amule CVS 20051015 does exactly the same thing: Read my shareddir file, find the 3.8 GB file, and die a horrible death.

This CVS is compiled with wxGTK2-2.6.0, which runs amule 2.0.3 with just a warning but which does not crash on the large file.

Can anybody please take a look at this bug?
Logged
A waste is a terrible thing to mind.