Post PtokaX DC Hub 0.3.3.21 bugs here! - Page 3
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

Post PtokaX DC Hub 0.3.3.21 bugs here!

Started by Madman, 08 August, 2005, 17:16:29

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Xico

#50
QuoteHub: $Lock EXTENDEDPROTOCOL6AypFPFxLMmUfXXtlRR1v2ZF@^Dwin Pk=PtokaX|
Client: $Supports BotINFO|
Is'n it supose for the client to send $Key after receving the $Lock?

Well, you did it, you should know. I'll  try your way.

Thanks

Edited.... later

Thanks PPK. I got what I wanted. My appoligizes for my desbelive. I should know that u knew :)

PPK

QuoteOriginally posted by Xico
Is'n it supose for the client to send $Key after receving the $Lock?
In old NMDC protocol yes, but we now use EXTENDEDPROTOCOL and PtokaX not need $Key if client send $Supports :))
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

Pedro?

i think i've got a very big problem , for one week ptokax crashes nearly every day and after that i often loose my connection and reboot is the only solution

here is the ptokaxdebug message :
---------------------------06/09/2005 13:06:05---------------------------
Exception 'ESocketError' in module PtokaX.exe at 000FB322
Windows socket error: Une op?ration sur un socket n'a pas pu ?tre effectu?e car le syst?me ne disposait pas de suffisamment d'espace dans la m?moire tampon ou parce que la file d'attente ?tait satur?e (10055), on API 'connect'

Call stack:
:004FC322 [PtokaX.exe]
:7C81EB33 [kernel32.dll]
:004FC322 [PtokaX.exe]
:00524C3B [PtokaX.exe]
:00526C86 [PtokaX.exe]
:005261D2 [PtokaX.exe]
Recursive call (2 times):
:004FC322 [PtokaX.exe]
:004FCABB [PtokaX.exe]
:004FC792 [PtokaX.exe]
:004FC7C2 [PtokaX.exe]
:004FD5BB [PtokaX.exe]
:00526080 [PtokaX.exe]
:004FD474 [PtokaX.exe]
:0050C13E [PtokaX.exe]
:77D18734 [USER32.DLL]
:77D18816 [USER32.DLL]
:77D185A4 [USER32.DLL]
:77D189CD [USER32.DLL]
:0050F9B7 [PtokaX.exe]
:77D196C7 [USER32.DLL]
:00566B58 [PtokaX.exe]
:00566B8F [PtokaX.exe]
:00566DAF [PtokaX.exe]
:00566DF2 [PtokaX.exe]
:00401B40 [PtokaX.exe] WinMain (PtokaX.cpp, line 43)
:005ADBBF [PtokaX.exe]
:00400000 [PtokaX.exe]
:7C816D4F [kernel32.dll]
:7C8399F3 [kernel32.dll]

Main Thread ID = 000009E4, Current Thread ID = 000009E4
Registers:
EAX = 0012FC24  CS = 001B  EIP = 7C81EB33  Flags = 00000202
EBX = 00002747  SS = 0023  ESP = 0012FC20    EBP = 0012FC74
ECX = 00000000  DS = 0023  ESI = 0012FCA8    FS  = 003B
EDX = 004FC322  ES = 0023  EDI = 00000000    GS  = 0000
Code at CS:EIP
5E C9 C2 10 00 85 FF 0F 8E E6 D0 FE FF 8B 55 FC
Stack:
004FCAEC 0EEDFADE 00000001 00000000 7C81EB33
00000000 00000000 7C8399F3 00525E05 01D097B4
005EC70B 01D1DB34 0000000B 00000000 01332200
7C8399F3 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF

Additional info:
Application Title : PtokaX DC Hub 0.3.3.21 [debug]
Major : 5
Minor : 1
Build : 2600
SP : 2
Type : 1
iJoins: 5197, iParts: 5172, iLogged: 24
NicklistLen : 294
OplistLen   : 100
MyInfosLen  : 0
MyInfosTagLen  : 2355
QueueA Size : 1024
QueueA Len : 0
QueueB Size   : 1024
QueueB Len   : 0
PQueue Size  : 1024
PQueue Len  : 0
HQueueA Size  : 1024
HQueueA Len  : 0
HQueueB Size  : 1024
HQueueB Len  : 0
OPQueueA Size  : 1024
OPQueueA Len  : 0
OPQueueB Size  : 1024
OPQueueB Len  : 0
InfoQueue Size  : 1024
InfoQueue Len  : 0
OPL-QueueA Size  : 1024
OPL-QueueA Len  : 0
OPL-QueueB Size  : 1024
OPL-QueueB Len  : 0
Q-QueueA Size  : 1024
Q-QueueA Len  : 0
Q-QueueB Size  : 1024
Q-QueueB Len  : 0

PPK

QuoteOriginally posted by Pedro?
i think i've got a very big problem
Is buggy borland component used for registering to hublist... disable "AutoRegister" on network page, sorry i am not able to fix it for next PtokaX version :(
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

blackwings

QuoteOriginally posted by PPK
QuoteOriginally posted by Pedro?
i think i've got a very big problem
Is buggy borland component used for registering to hublist... disable "AutoRegister" on network page, sorry i am not able to fix it for next PtokaX version :(
hmm, but without the autoregister, peoples hubs wont get registered = no new user,
its surprising no one has reported this bug before. PPK, when do you think you can fix it?
(you said it was a borland problem, have they said anything about when they maybe have fixed the hub?)


Pedro?

thx for ur answer i disabled autoregister hope i could get new users anyway

i also got another bug but there is nothing about it in ptokaxdebug.log ptokax just doesn't answer anymore i'll tell you if it keeps on happening

uffetjur

Can't get rid of hublist pinger
hasnt had AutoRegister enabled in monts
still my hub is registrered

Is the only way to stop it bye mailing hublist.org?
Somewhere in Cyberspace

PPK

QuoteOriginally posted by blackwings
hmm, but without the autoregister, peoples hubs wont get registered = no new user
In hublist.org you don't need to use register function in hub, you only add url to hub on hublist.org webpage and pinger do all other work...
QuoteOriginally posted by blackwings
its surprising no one has reported this bug before.
Is reported more times for more PtokaX versions, this one is on socket connect and here is another one (crashing more) on close socket X(
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

hutchenky

with prokax 1708 zion 1.14 and mdc 2.0 works fine but the 21 ptokax version anytime i check i got disconnected, wouldn't it be better to relaese a ptokax version when it is working ok instead of every moth a new version full with bugs?

bastya_elvtars

QuoteOriginally posted by hutchenky
with prokax 1708 zion 1.14 and mdc 2.0 works fine but the 21 ptokax version anytime i check i got disconnected, wouldn't it be better to relaese a ptokax version when it is working ok instead of every moth a new version full with bugs?

Haven't you checked your brain before using your mouth? PtokaX disconnects some buggy client. If you wanted a real solution, instead of criticising, you would have posted a log from the admin chat or something similar, or at least a better description of the problem. Also, if you wanna join the dev team, PPK will surely allow, but first watch your words, and try to fix the bugs in your own brain before using it. What I mean is:

Quotebut the 21 ptokax version anytime i check i got disconnected

What does check mean?
Everything could have been anything else and it would have just as much meaning.

hutchenky

Than explain to me why both 2 clients worked ok with 1708 and not with 21?

hutchenky

But problem with 1708 versie is a pop up screen saying access violation, this freeses ptokax.
And isn't this a board to report bugs?

Tw?sT?d-d?v

QuoteOriginally posted by hutchenky
But problem with 1708 versie is a pop up screen saying access violation, this freeses ptokax.
And isn't this a board to report bugs?

If you got this then you should have a crash report.

what do you get told when you try to connect with the 2 clients?

hutchenky

Exception 'EAccessViolation' in module PtokaX.exe at 0009DA08
Access violation at address 0049EA08 in module 'PtokaX.exe'. Read of address 00000032

bastya_elvtars

QuoteOriginally posted by hutchenky
Exception 'EAccessViolation' in module PtokaX.exe at 0009DA08
Access violation at address 0049EA08 in module 'PtokaX.exe'. Read of address 00000032

Post the contents of ptokaxdebug.log
Everything could have been anything else and it would have just as much meaning.

hutchenky

---------------------------5-9-2005 0:00:42---------------------------
Exception 'EAccessViolation' in module PtokaX.exe at 0009DA08
Access violation at address 0049EA08 in module 'PtokaX.exe'. Read of address 00000032

Call stack:
:0049EA08 [PtokaX.exe] hashRegMan::Find (hashRegMan.cpp, line 183)
:004044AA [PtokaX.exe] ThubForm::CheckRegistered (frmHub.cpp, line 337)
:0049A423 [PtokaX.exe] cDcCommands::ValidateUserNick (DcCommands.cpp, line 3091)
:77D1882A [USER32.dll]
:77D1C63F [USER32.dll]
:7C9106EB [ntdll.dll]
:7C91056D [ntdll.dll]
:71A116A3 [wshtcpip.dll]
:71A2150C [WS2HELP.dll]
:016965B4 [nl_lsp.dll]
:719D44B0 [MSWSOCK.dll]
:0169293F [nl_lsp.dll]
:01693C20 [nl_lsp.dll]
:00494357 [PtokaX.exe] cDcCommands::ValidateNick (DcCommands.cpp, line 2381)
:0048B22D [PtokaX.exe] cDcCommands::Key (DcCommands.cpp, line 820)
:0048787E [PtokaX.exe] cDcCommands::ProcessData (DcCommands.cpp, line 290)
:71A34379 [WS2_32.dll]
:71A34382 [WS2_32.dll]
:71A52EA3 [WSOCK32.DLL]
:004518E8 [PtokaX.exe] clsUser::ProcessLines (clsUser.cpp, line 647)
:0045184A [PtokaX.exe] clsUser::DoRecv (clsUser.cpp, line 622)
:01695684 [nl_lsp.dll]
:005333EB [PtokaX.exe]
:00535382 [PtokaX.exe]
:0053336A [PtokaX.exe]
:005333EC [PtokaX.exe]
:005B0A43 [PtokaX.exe]
:00533270 [PtokaX.exe]
:00451BB8 [PtokaX.exe] clsUser::SetIP (clsUser.cpp, line 761)
:00459DF7 [PtokaX.exe] theLoop::AcceptUser (serviceLoop.cpp, line 210)
:005333EC [PtokaX.exe]
:005B0A65 [PtokaX.exe]
:00533270 [PtokaX.exe]
:77D18C3A [USER32.dll]
:00578AD4 [PtokaX.exe]
:77D18C4E [USER32.dll]
:00578AB2 [PtokaX.exe]
:0051FAA5 [PtokaX.exe]
:004598A2 [PtokaX.exe] theLoop::ProcessAccepts (serviceLoop.cpp, line 115)
:00459FAF [PtokaX.exe] theLoop::FOnTimer (serviceLoop.cpp, line 255)
:005A1EB1 [PtokaX.exe]
:005F7C0D [PtokaX.exe]
:77D2F3E3 [USER32.dll]
:0046E0CF [PtokaX.exe] LuaScriptsSet::GetGcInfo (luaInterface.cpp, line 4030)
:77D1EB3E [USER32.dll]
:746B0E6C [MSCTF.dll]
:00578B66 [PtokaX.exe]
:00578A4C [PtokaX.exe]
:0051AD66 [PtokaX.exe]
:77D18734 [USER32.dll]
:77D18816 [USER32.dll]
:77D189CD [USER32.dll]
:0051E5DF [PtokaX.exe]
:77D196C7 [USER32.dll]
:00575780 [PtokaX.exe]
:005757B7 [PtokaX.exe]
:005759D7 [PtokaX.exe]
:00575A1A [PtokaX.exe]
:00401B44 [PtokaX.exe] WinMain (PtokaX.cpp, line 43)
:005BE663 [PtokaX.exe]
:00400000 [PtokaX.exe]
:7C816D4F [kernel32.dll]
:7C8399F3 [kernel32.dll]

Main Thread ID = 00000DE8, Current Thread ID = 00000DE8
Registers:
EAX = 00E62630  CS = 001B  EIP = 0049EA08  Flags = 00010212
EBX = 0000005B  SS = 0023  ESP = 0012F8AC    EBP = 0012F8BC
ECX = 0000001E  DS = 0023  ESI = 00578B54    FS  = 003B
EDX = 0000001E  ES = 0023  EDI = 0012FE38    GS  = 0000
Code at CS:EIP
8B 4A 14 8B 45 0C 3B 88 54 01 00 00 75 0B 8B 55
Stack:
0000005B 00E62630 0000005B 0000001E 0012F8D8
00000000 00000000 7C8399F3 00534A05 01C3EC00
005FD30B 00E7A120 0000000B 00000000 00E82844
7C8399F3 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF

Additional info:
Application Title : PtokaX DC Hub 0.3.3.0 build 17.08 [debug]
Major : 5
Minor : 1
Build : 2600
SP : 2
Type : 1
iJoins: 23597, iParts: 23512, iLogged: 84
NicklistLen : 964
OplistLen   : 87
MyInfosLen  : 7718
MyInfosTagLen  : 7718
QueueA Size : 15
QueueA Len : 0
QueueB Size   : 15
QueueB Len   : 0
PQueue Size  : 169
PQueue Len  : 0
HQueueA Size  : 97
HQueueA Len  : 0
HQueueB Size  : 69
HQueueB Len  : 0
OPQueueA Size  : 566
OPQueueA Len  : 0
OPQueueB Size  : 308
OPQueueB Len  : 0
InfoQueue Size  : 566
InfoQueue Len  : 0
OQ-QueueA Size  : 229
OQ-QueueA Len  : 0
OQ-QueueB Size  : 33
OQ-QueueB Len  : 0

bastya_elvtars

Oh, this is easy. Do not use NetLimiter.
Everything could have been anything else and it would have just as much meaning.

hutchenky

i don't use netlimiter

hutchenky

I think it is a certain user connecting to the hub, maybe he got netlimiter, but i am not using my netlimiter for ages

bastya_elvtars

QuoteOriginally posted by hutchenky
I think it is a certain user connecting to the hub, maybe he got netlimiter, but i am not using my netlimiter for ages

Have it installed?
Everything could have been anything else and it would have just as much meaning.

hutchenky

Yes it is installed, so you know for sure my netlimiter causes the acces violation in 1708? if that is so i use the 1708 again instead of the 21, thnx mate

bastya_elvtars

QuoteOriginally posted by hutchenky
Yes it is installed, so you know for sure my netlimiter causes the acces violation in 1708? if that is so i use the 1708 again instead of the 21, thnx mate

If you don't use it, uninstall it, cause your whole system will be unstable.
Everything could have been anything else and it would have just as much meaning.

blackwings

#72
QuoteOriginally posted by hutchenky
Than explain to me why both 2 clients worked ok with 1708 and not with 21?
well, since 0.3.3.0 b17.09 and later, ptokax doesn't accept buggy $Supports from DC clients,
for example rmDC can't acces ptokax anymore because of its buggy $Supports.

btw nmdc v2 is a crappy old client, use DC++ instead. And Zion, its a OP client right, use DCDM++ instead of Zion.
With those changes, you can use 0.3.3.21 :)


PPK

QuoteOriginally posted by hutchenky
with prokax 1708 zion 1.14 and mdc 2.0 works fine but the 21 ptokax version anytime i check i got disconnected
Please enable CMDs in Users/Chat tab and post what this clients send... Maybe is bug in PtokaX and maybe is bug in bad protocol support in this clients :rolleyes: Zion is mod of StrongDC++, StrongDC++ is mod CZDC++ and CZDC++ is mod of DC++... nice way to create very buggy client :D
QuoteOriginally posted by hutchenky
wouldn't it be better to relaese a ptokax version when it is working ok instead of every moth a new version full with bugs?
Are you really sure that you don't want next 10 years new PtokaX version because will be always full of bugs  ?( :D
And btw i release PtokaX always only when is working  :P
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

uffetjur

damn finally a crash
--------------------------------

Access violation at address 77F5215E in module 'ntdll.dll'. Write of address 67676F66

Call stack:
:77F5215E [ntdll.dll]
:77F51FBF [ntdll.dll]
:71A423AE [MSWSOCK.dll]
:71AA19F7 [WS2_32.dll]
:71AA123A [WS2_32.dll]
:71AA1A1F [WS2_32.dll]
:00533BF0 [PtokaX.exe]
:00452640 [PtokaX.exe] clsUser::DoRecv (clsUser.cpp, line 517)
:0053406B [PtokaX.exe]
:77F82402 [ntdll.dll]
:00451590 [PtokaX.exe] clsUser::~clsUser (clsUser.cpp, line 163)
:0045A9C6 [PtokaX.exe] theLoop::ProcessAccepts (serviceLoop.cpp, line 96)
:0045B019 [PtokaX.exe] theLoop::FOnTimer (serviceLoop.cpp, line 236)
:0045B02C [PtokaX.exe] theLoop::FOnTimer (serviceLoop.cpp, line 238)
:005A214B [PtokaX.exe]
:005A2641 [PtokaX.exe]
:005A26D9 [PtokaX.exe]
:005F83DD [PtokaX.exe]
:0046ED18 [PtokaX.exe] LuaInterpret::GetGC (luaInterface.cpp, line 4136)
:0057938E [PtokaX.exe]
:00579274 [PtokaX.exe]
:0051B58E [PtokaX.exe]
:77D57B5B [USER32.dll]
:77D5CE12 [USER32.dll]
:77D34435 [USER32.dll]
:77D34D38 [USER32.dll]
:00575FA8 [PtokaX.exe]
:00575FDF [PtokaX.exe]
:005761FF [PtokaX.exe]
:00576242 [PtokaX.exe]
:00401B44 [PtokaX.exe] WinMain (PtokaX.cpp, line 43)
:005BEE77 [PtokaX.exe]
:00400000 [PtokaX.exe]
:77E962B6 [kernel32.dll]

Main Thread ID = 000005B8, Current Thread ID = 000005B8
Registers:
EAX = 67676F62  CS = 001B  EIP = 77F5215E  Flags = 00010206
EBX = 013E0000  SS = 0023  ESP = 0012FAF8    EBP = 0012FB04
ECX = 013E7380  DS = 0023  ESI = 01DAE000    FS  = 003B
EDX = 01DAEBA0  ES = 0023  EDI = 01DAEBA0    GS  = 0000
Code at CS:EIP
89 48 04 74 45 8A 47 05 A8 04 0F 85 92 A7 03 00
Stack:
013E0000 01DAEA98 00000001 0012FBD8 77F51FBF
00000000 00000000 77E962B6 00535205 01478FEC
005FDB0B 00EAFF84 0000000B 00000000 00EAF2C8
77E962B6 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF

Additional info:
Application Title : PtokaX DC Hub 0.3.3.1 [debug]
Major : 5
Minor : 1
Build : 2600
SP : 0
Type : 1
iJoins: 75307, iParts: 75102, iLogged: 204
NicklistLen : 3864
OplistLen   : 140
MyInfosLen  : 10253
MyInfosTagLen  : 19132
QueueA Size : 1606
QueueA Len : 0
QueueB Size   : 894
QueueB Len   : 0
PQueue Size  : 1720
PQueue Len  : 0
HQueueA Size  : 96
HQueueA Len  : 0
HQueueB Size  : 59
HQueueB Len  : 0
OPQueueA Size  : 291
OPQueueA Len  : 0
OPQueueB Size  : 223
OPQueueB Len  : 0
InfoQueue Size  : 148
InfoQueue Len  : 0
OQ-QueueA Size  : 1422
OQ-QueueA Len  : 0
OQ-QueueB Size  : 907
OQ-QueueB Len  : 0
Somewhere in Cyberspace

SMF spam blocked by CleanTalk