aMule Forum
English => en_Bugs => Topic started by: GuybrushThreepwood on May 18, 2012, 06:35:41 PM
-
Hello to everyone. The latest SVN I've built before yesterday was 10494 and it has always worked like a charm including the same version aMuleGUI (built both under MinGW and i686-linux). Yesterday I've built 10781 before and 10788 soon after. The both of them work well on the daemon side while aMuleGUI (the same version respectively) refuses any connection attempt complaining about a wrong password when it isn't true.
Here is what I've done:
1) I've checked everything with passwords and amule.conf, generated new passwords too, everthing to no avail
2) I've built both MinGW Win32 version and Linux version of aMuleGUI 10781 and 10788. Both of the toolchains are fine. Still the same
3) I've cross-compiled mips-linux 10781 and 10788 (I run the daemon on a mips-router) to resemble the respective aMuleGUI versions everytime
I don't know if you've received any other reports about this issue but it seems to me that there could be something wrong with aMuleGUI...
I'd like to point out that all the three toolchains (MinGW Win32, i686-linux and mips-linux) I use are perfectly fine and, apart from the newly added wxWidgets 2.8.12 (2.8.10 before) they're the same as ever. I've also tried to setup again from scratch che MinGW toolchain to no avail.
Thanks for your advices and have a good day!
-
Please try 10764. There was a bugfix regarding EC endianness in 10765 which might be related to the problem.
If 10764 works, try 10765 to confirm it is really that.
-
Ha.
Old code:
- Always swap low to high
- Pass the swapped integer to PokeUInt32 which swaps again on big endian.
New code:
- Swap on little endian
- Pass the little endian swapped integer to PokeUInt32 which swaps again on big endian. So the result is always swapped.
Kind of confusing, yeah.
-
Don't worry, I've understood what you're talking about. I've already built Win32 aMuleGUI under MinGW, both 10763 and 10765 and in the next days I would build i686-linux aMuleGUI and the mips-linux daemon for each version then I would post here the results but I'm rather confident that the problem is there.
-
Hello again! I was too curious to check if your theory was correct (I was already almost sure about that but I couldn't wait to verify it ;) ) and I've fought to find the time to do all the necessary compilation work.
I've built everything for both 10763 and 10765 so aMuleGUI (both Win32 and i686-linux) and the respective versions amuled mips-linux and I can confirm that you were completely right as it often (if not always at least for what I can say) happens, Stu.
aMuleGUI 10763 (I've tested both the versions with their respective daemons as I never mix versions up) works flawlessly while 10765 complains about the password being wrong.
To get the newer SVNs working then there is 'only' some patching to do because I believe that there are more than valid reasons if the change was made in 10765 and reverting back to the previous solution is quite unlikely to happen... Thanks as always! :)
-
Good to hear we have located the root of the problem.
I think we can probably just revert 10765, but I'm waiting for GonoszTopi to comment on the issue. Just give it a bit of time, he doesn't have much time for the project at the moment.
-
Kind of confusing, yeah.
Yeah. >:( It was. Now the behaviour is reverted, but not the code.
Btw, thanks for all your patience.