mldonkey-bugs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Mldonkey-bugs] [bugs #3989] Segfault after a BT commit


From: spiralvoice
Subject: [Mldonkey-bugs] [bugs #3989] Segfault after a BT commit
Date: Tue, 02 Dec 2003 14:16:33 -0500
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.5) Gecko/20031007

This mail is an automated notification from the bugs tracker
 of the project: mldonkey, a free e-Donkey client.

/**************************************************************************/
[bugs #3989] Latest Modifications:

Changes by: 
                spiralvoice <address@hidden>
'Date: 
                Tue 12/02/2003 at 20:16 (Europe/Berlin)

            What     | Removed                   | Added
---------------------------------------------------------------------------
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
This bug has already been solved in the current version.

Please download it and report a new bug if the problem still exists

- spiralvoice






/**************************************************************************/
[bugs #3989] Full Item Snapshot:

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=3989>
Project: mldonkey, a free e-Donkey client
Submitted by: 0
On: Sun 06/15/2003 at 23:46

Category:  Core
Severity:  5 - Average
Item Group:  Segmentation Fault
Resolution:  None
Assigned to:  None
Status:  Closed
Release:  None
Release:  2.5.3
Platform Version:  Linux i386-i686
Binaries Origin:  Compiled From CVS


Summary:  Segfault after a BT commit

Original Submission:  This was my first BT attempt.

Everything went fine, file was committed (and split correctly), but few moments 
later core crashed with

Exception md4_safe_fd: Read failed: Is a directory in Select.loop

zsh: segmentation fault  ./mlnet -stdout



After restarting the core the file reappeared in the downloads, and resumed 
downloading, that time over 100%. So another bug may exist (like, "save" should 
be forced after any file commit)



Follow-up Comments
------------------


-------------------------------------------------------
Date: Tue 12/02/2003 at 20:16       By: spiralvoice
This bug has already been solved in the current version.

Please download it and report a new bug if the problem still exists

- spiralvoice

-------------------------------------------------------
Date: Wed 11/05/2003 at 20:18       By: None
See patch #2254

-------------------------------------------------------
Date: Tue 11/04/2003 at 22:35       By: None
(untested)

--- src/networks/bittorrent/bTInteractive.ml    9 Oct 2003 12:23:07 -00001.8

+++ src/networks/bittorrent/bTInteractive.ml    4 Nov 2003 21:21:21 -0000

@@ -74,6 +74,7 @@

         if file.file_files <> [] then 

           let old_file = new_name ^ ".torrent" in

           Sys.rename new_name old_file;

+         set_file_disk_name file old_file;

           let old_fd = Unix32.create_ro old_file in

           List.iter (fun (filename, begin_pos, end_pos) ->

               let filename = Filename.concat new_name filename in



?



-------------------------------------------------------
Date: Tue 10/14/2003 at 23:56       By: None
still in 2.5-4;



bittorrents consisting of just one file are ok. when i move them from the 
incoming, there's no problem.

however, when a bt file consists of multiple files, and i move the extra file 
dir that is created in the incoming/BT dir, or the .torrent file in the BT dir, 
mlnet crashes. after restarting, above mentioned behavior occurs.



but when i (re)move the files from *within* the newly created dir, without 
moving the dir itself, there's also no problem.












For detailed info, follow this link:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=3989>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]