Actual Crashes

[melobern]

:information_source: This issue must be closed at the very end of the project. Until then, we add every command that made the server crash. We check them when we solve them and will happily retest them later :tada:

• [ ] JOIN #42, #l l ,#43 . To test it without the interactive mode :

  echo "PASS pass\r\nNICK nick\r\nUSER a a a :a\r\nJOIN #42, #l l  ,#43" | nc -C 127.0.0.1 6667

• [ ] Do PASS <valid pass> 3 times before registration. To test it without the interactive mode :

  echo "PASS pass\r\nPASS pass\r\nPASS pass\r\nPASS pass\r\nPASS pass\r\nNICK nick\r\nUSER a a a :a\r\nJOIN #42, #l l  ,#43" | nc -C 127.0.0.1 6667

• [ ] Do QUIT after having joined one or more channel. To test it without the interactive mode :

  echo "PASS pass\r\nNICK nick\r\nUSER a a a :a\r\nJOIN #42\r\nQUIT" | nc -C 127.0.0.1 6667

[faboussard]

crash apres un essai de connexion infructueux :

➜  irc git:(kick) ✗ nc -C localhost 6667
pass pass 
nick ni
user ni 0 *:realname
:ircserv.localhost 461 ni USER :Not enough parameters
join #s
:ircserv.localhost 451 ni :You have not registered
pass pass
:ircserv.localhost 462 ni :You may not reregister
nick ni
join #s
:ircserv.localhost 451 ni :You have not registered
join
:ircserv.localhost 451 ni :You have not registered
pass 
:ircserv.localhost 462 ni :You may not reregister
pass pass
nc: write failed (0/2): Broken pipe

[faboussard]

netcat: crash apres un quit suivi dun join 0 (car on fait un part alors que plus rien nexiste...). a tester sur hexchat

:nick PART #s : say goodbye!
quit
join 0
nc: write failed (0/2): Broken pipe

EDIT : NOT AN ISSUE - NETCAT CANNOT CONTACT SERVER AFTER QUIT

[ysengoku]

netcat: crash apres un quit suivi dun join 0 (car on fait un part alors que plus rien nexiste...).

a tester sur hexchat

:nick PART #s : say goodbye!

quit

join 0

nc: write failed (0/2): Broken pipe

Pour moi, ce n'est pas un Crash mais un comportement normal. Au moment où un client a fait QUIT, il n'est plus connecté au server, donc fd est fermé (= write failed). Le message vient du nc. Et je ne pense pas que le server puisse fermer le nc. C'est sur le terminal où le nc est lancé que l'on pourra arrêter le programme nc.