aMule Bug Tracker - aMule
View Issue Details
0001188aMuleSearchpublic2007-10-04 09:272008-01-13 01:11
Gnucco 
Kry 
normalmajoralways
resolvedfixed 
SVN 
SVN 
Linux (Ubuntu 7.04)
0001188: Tag list read/write cycle corrupts data
I read a tag list from a binary packet stored in a CMemFile object.

Writing the same taglist to another MemFile, the binary output is different from the original binary input.

To reproduce the bug, simply put the attached cpp file in src dir, and add

  #include "amule_taglist_selftest.cpp"

somewhere at the bottom of amule.cpp.

The attached source file contains two taglist dump captured directly from a live kad session.

IMHO, some sort of self-test could be added to amule startup.
No tags attached.
cpp amule_taglist_selftest.cpp (5,773) 2007-10-04 09:27
https://bugs.amule.org/file_download.php?file_id=202&type=bug
cpp amule_taglist_selftest.cpp (6,577) 2007-10-04 09:29
https://bugs.amule.org/file_download.php?file_id=203&type=bug
cpp amule_taglist_selftest.cpp (6,723) 2007-10-04 20:27
https://bugs.amule.org/file_download.php?file_id=204&type=bug
Issue History
2007-10-04 09:27GnuccoNew Issue
2007-10-04 09:27GnuccoFile Added: amule_taglist_selftest.cpp
2007-10-04 09:27GnuccoOperating System => Linux (Ubuntu 7.04)
2007-10-04 09:29GnuccoNote Added: 0002422
2007-10-04 09:29GnuccoFile Added: amule_taglist_selftest.cpp
2007-10-04 20:27GnuccoFile Added: amule_taglist_selftest.cpp
2007-10-04 20:29GnuccoNote Added: 0002424
2007-10-05 23:34KryStatusnew => assigned
2007-10-05 23:34KryAssigned To => Kry
2008-01-13 01:11XaignarStatusassigned => resolved
2008-01-13 01:11XaignarFixed in Version => SVN
2008-01-13 01:11XaignarResolutionopen => fixed
2008-01-13 01:11XaignarNote Added: 0002506

Notes
(0002422)
Gnucco   
2007-10-04 09:29   
Oops... sorry, use this file, the prev one is broken
(0002424)
Gnucco   
2007-10-04 20:29   
Oops... I have no credibility, I know... :(
please, use the last .cpp file I attached. The first two are broken. sorry

nevertheless, the bug is real!
(0002506)
Xaignar   
2008-01-13 01:11   
Thank you for repporting the problem. The bug has now been (properly) fixed.

Cheers.