aMule Forum

English => en_Bugs => Topic started by: greaman on April 17, 2004, 06:16:35 PM

Title: new problem with rc2 ;) ignored tag/read after eof
Post by: greaman on April 17, 2004, 06:16:35 PM

now I got a new crash error, so see rc2 crashing isn't realy boring :)

CPartFile::CPartFile(CSearchfile*): ignored tag 0x15=1

after many repeats of this Error amule crashes with: Read after EOF

couldn't reproduce it yet, but I'm working on it for a trace...hehe

Title: Re: new problem with rc2 ;) ignored tag/read after eof
Post by: Jacobo221 on April 18, 2004, 01:27:31 AM

Yes, please, a backtrace would be much better :-) We look forward for it.

Thanks and greetings.

Title: Re: new problem with rc2 ;) ignored tag/read after eof
Post by: Kry on April 18, 2004, 02:06:45 AM

that's not a error :P

The read after EOF is very interesting. if you get it again, notice us the crashing lines

Title: Re: new problem with rc2 ;) ignored tag/read after eof
Post by: greaman on April 18, 2004, 02:28:14 AM

I would have posted the backtrace lines if there would have been some ;)

There was just the tag error... the read after eof and the emule crashed without further messages. When Rc2 crashes in 50% of the cases I don't get a backtrace.

Hmm and okay... so its not an error :) lets call it a  feature :] hehehe

Title: Re: new problem with rc2 ;) ignored tag/read after eof
Post by: greaman on April 23, 2004, 12:23:12 AM

another RaEOF has shown up.. this time amule didn't crash

Sharing /home/greaman/.xMule/Temp/120.part.met
Sharing /home/greaman/.xMule/Temp/124.part.met
Sharing /home/greaman/.xMule/Temp/128.part.met
Save ServerCount = 267 /0x10B/
Saved ServerCount endian = 267 /0x10B/
Read After End Of File!!!!
Wrong Tags on hello type packet - short packet on read (corrupted tagcount?)

Sent by http://emule-project.net on ip 80.35.171.190 port 4662 using client 36 version 3c
User Disconnected.


no backtrace, no information which file is meant

Title: Re: new problem with rc2 ;) ignored tag/read after eof
Post by: Kry on April 23, 2004, 12:33:40 AM

because that's not an error, only info, as the CTag one.


Is caused by a wrong packet.