Assert failed: infoParts.Length

Bug #949476 reported by ile
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
IRC.NET
Fix Committed
Medium
Alexander Regueiro

Bug Description

Not sure if this is really a bug, but still an issue of some kind maybe?

See the screenshot.

Revision history for this message
ile (ilkkah) wrote :
Revision history for this message
ile (ilkkah) wrote :

Maybe the code could do parsing, like extract the info (ServerClientsCount, ServerServersCount) from the message with regexps?

Revision history for this message
Alexander Regueiro (alexreg) wrote :

Sounds like you're connecting to a non-standard/compliant server. Maybe you could paste the traffic log (see trace/debug window).

Revision history for this message
ile (ilkkah) wrote :

Sure, here you are. There was something strange in there (Unknown IRC message command '042').

I don't see that particular line in which was in the screenshot though.

01:19:46 Connecting to server...
01:19:47 Connected to server at 'Unspecified/irc.inet.fi:6667'.
01:19:47 () <<< PASS :
01:19:47 () <<< NICK :ilexxxxx
01:19:47 () <<< USER ilexxxxx 0 * :ilexxxxx
01:19:48 Unknown IRC message command '020'.
01:19:48 () >>> :irc1.inet.fi 020 * :Please wait while we process your connection.
'UI Task' (Managed): Loaded 'System.SR.dll'
A first chance exception of type 'System.IO.EndOfStreamException' occurred in mscorlib.dll
01:19:48 () >>> :irc1.inet.fi 461 * PASS :Not enough parameters
01:19:48 () >>> :irc1.inet.fi 001 ilexxxxx :Welcome to the Internet Relay Network ilexxxxx!~ilexxxxx@------.dhcp.inet.fi
01:19:48 () >>> :irc1.inet.fi 002 ilexxxxx :Your host is irc1.inet.fi, running version 2.11.2p3
01:19:48 () >>> :irc1.inet.fi 003 ilexxxxx :This server was created Thu Sep 15 2011 at 17:57:40 EEST
01:19:48 () <<< JOIN :
01:19:48 () >>> :irc1.inet.fi 004 ilexxxxx irc1.inet.fi 2.11.2p3 aoOirw abeiIklmnoOpqrRstv
01:19:48 () >>> :irc1.inet.fi 005 ilexxxxx RFC2812 PREFIX=(ov)@+ CHANTYPES=#&!+ MODES=3 CHANLIMIT=#&!+:30 NICKLEN=15 TOPICLEN=255 KICKLEN=255 MAXLIST=beIR:64 CHANNELLEN=50 IDCHAN=!:5 CHANMODES=beIR,k,l,imnpstaqr :are supported by this server
01:19:48 () >>> :irc1.inet.fi 005 ilexxxxx PENALTY FNC EXCEPTS=e INVEX=I CASEMAPPING=ascii NETWORK=IRCnet :are supported by this server
01:19:48 Unknown IRC message command '042'.
01:19:48 () >>> :irc1.inet.fi 042 ilexxxxx 246EAAQOU :your unique ID
01:19:48 () >>> :irc1.inet.fi 251 ilexxxxx :There are 58417 users and 7 services on 36 servers
01:19:48 () >>> :irc1.inet.fi 252 ilexxxxx 104 :operators online
01:19:48 () >>> :irc1.inet.fi 253 ilexxxxx 1 :unknown connections
01:19:48 () >>> :irc1.inet.fi 254 ilexxxxx 33330 :channels formed
A first chance exception of type 'System.IO.EndOfStreamException' occurred in mscorlib.dll
Silverlight AppDomainAssertAssertion Failed
   at DefaultTraceListener.AssertFailure(String File, Int32 Line, String Expr)
   at DefaultTraceListener.Fail(String message, String detailMessage)
   at DefaultTraceListener.Fail(String message)
   at TraceInternal.Fail(String message)
   at TraceInternal.Assert(Boolean condition)
   at Debug.Assert(Boolean condition)
   at IrcClient.ProcessMessageLUserMe(IrcMessage message)
   at IrcClient.ReadMessage(IrcMessage message, String line)
   at IrcClient.ReceiveCompleted(Object sender, SocketAsyncEventArgs e)
   at SocketAsyncEventArgs.OnCompleted(SocketAsyncEventArgs e)
   at SocketAsyncEventArgs.OnCompletedInternal(SocketAsyncEventArgs e)
   at SocketAsyncEventArgs.FinishOpera

Revision history for this message
Alexander Regueiro (alexreg) wrote :

Okay, I agree this is probably a deficiency in the message handling routines. It could be the server acting non-compliantly, but the IRC protocol can be rather vague, and this is one of the instances. I've provided a fix anyway, and it should be available on the GitHub repo now.

Changed in ircdotnet:
assignee: nobody → Alex Regueiro (alexreg)
importance: Undecided → Medium
status: New → Confirmed
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.