Krekon 0 Posted February 12, 2017 Share Posted February 12, 2017 I am working right now on improving a random basic client and working a lot on it . It has the syserr.txt file but inside even if the client has an error dosen't display anything , until now i didn't need it that much because i could figure what i have done wrong and fix it but right now i really need to see the errors . Does anyone knows why the syserr it's not working ? Thank you anticipated . Link to comment Share on other sites More sharing options...
Premium Galet 512 Posted February 12, 2017 Premium Share Posted February 12, 2017 Give us your syserr and we'll see what's the problem. Just kidding Have you ever messed up something related to the syserr ? It seems to always be there, also it depends of your error (try to purposedly corrupt one of your .py files - TypeError... - and see if the syserr is displaying something) Also try to compile in debug mode, to have additional backtraces and so on... Also check the last thing you modified in sources Have a nice day Link to comment Share on other sites More sharing options...
Krekon 0 Posted February 12, 2017 Author Share Posted February 12, 2017 15 minutes ago, Galet said: Give us your syserr and we'll see what's the problem. Just kidding Have you ever messed up something related to the syserr ? It seems to always be there, also it depends of your error (try to purposedly corrupt one of your .py files - TypeError... - and see if the syserr is displaying something) Also try to compile in debug mode, to have additional backtraces and so on... Also check the last thing you modified in sources Have a nice day You really got me there with the first line I didn't messed nothing related to syserr as i said i saw this problem long time ago so it seems that the client is like that . I tried purposedly corrupt files but if the corruption is too small nothing happend but that client dosen't work . I saw now that if the problem is too severe a log display when i try to launch the .exe but it's not helping too much because there it's showing the final reason like _pack_ could not be load due to bad files or some similar things , not like that syserr which would show you the file and the lines . It's not a big deal i mean it's just a lot to work not knowing where the problem is exactly and i loose more time . I thought that somebody have some information about this problem . PS : I'm working on it without source since i was out of this line for years and i try to remember and learn all the new things step by step . Link to comment Share on other sites More sharing options...
Premium Solution ragem0re 155 Posted February 12, 2017 Premium Solution Share Posted February 12, 2017 If you don't use the source, it could be possible that the publisher of the binary commented all the syserr lines in the source. What binary is it? Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now