Possible Bug w/ ApexDC++ socket handling

[Naithif]

Check this out...

Sorry for the delay on Beta3, but we've decided to send it to our testers and give them a few days on it.

We've been able to nail reason for this crash. If you're on Beta 1/2, stay out of Ptokax enabled hubs, otherwise it will crash your client. To find out whether the hub is Ptokax, it should say in the MOTD (the message dispalyed when connecting to the hub).

Use hublist.org to connect to non-ptokax hubs.

(link)

How nice... the developers advise people to leave PtokaX hubs and use the bugged, beta version of their client instead of using the older, but stable versions...

[CrazyGuy]

Hmm, and they got it all wrong 
Time to pay them a visit 
The link however seems to not work :-\

[Naithif]

The whole site seems to be down right now ???

Edit: It's back online

[bastya_elvtars]

Yeah, this is like: my driver won't uninstall, I nned to clean it manually, M$ R T3H SUXX0rZ!!!11

[CrazyGuy]

I've had a talk with Lee about this issue.
He's aware this is a problem in Apex which is as good as fixed already.

[Typhoon]

why blame PtokaX like that then ..
or is he trying to play a DC Deaf nerd?

[PPK]

Well... ApexDC++ is not Direct Compatible, if users of this client stay out Direct Connect hub (not only Ptokax but all of them) then it will be good

[CrazyGuy]

testresults show that PtokaX 0.3.5.2 itself crashes when ApexDC++ 1.0.0B2 tries to connect. 
PPK will look into this, and I'm also seeing if I can get more info from ApexDC++ side.

Some additional information:

PtokaX 0.3.5.2 crashes with error notification

[ERR] Exception logged: Exception 'EAccessViolation' in module ntdll.dll at 0003326D
Access violation at address 7C93426D in module 'ntdll.dll'. Read of address 00000000

Also ApexDC++ can crash with the following error

Code: c0000005 (Access violation)
Version: 1.0.0B (2007-04-09)
Major: 5
Minor: 1
Build: 2600
SP: 2
Type: 1
Time: 2007-04-10 12:11:21
TTH: TKIC3A5ZDYMVOAH5PD722A77JWZ6AGMKBK6OQWA

ntdll!0x7C918FEA: RtlpWaitForCriticalSection
ntdll!0x7C90104B: RtlEnterCriticalSection
d:\cvs\apexdc++\trunk\client\user.h(114): Identity::getNick
d:\cvs\apexdc++\trunk\windows\hubframe.cpp(782): HubFrame::onSpeaker
d:\cvs\apexdc++\trunk\windows\hubframe.h(74): HubFrame::ProcessWindowMessage

What causes these crashes is still unknown.
More tests however have shown that PtokaX 0.3.5.2c and newer do not have this problem with this client

[14:33:34] *** Connecting to 127.0.0.1...
[14:33:34] *** Connected
[14:33:35] <PtokaX> This hub is running PtokaX DC Hub 0.3.5.2c Dec  4 2006 22:53:07 (UpTime: 0 days, 0 hours, 0 minutes)


[14:35:37] *** Connecting to 127.0.0.1...
[14:35:37] *** Connected
[14:35:38] <PtokaX> This hub is running PtokaX DC Hub 0.3.5.2d Jan  7 2007 19:50:37 (UpTime: 0 days, 0 hours, 0 minutes)



[14:32:31] *** Connecting to 127.0.0.1...
[14:32:31] *** Connected
[14:32:32] <PtokaX> This hub is running PtokaX DC Hub 0.3.5.2e Jan 23 2007 14:26:02 (UpTime: 0 days, 0 hours, 0 minutes)



[14:12:20] *** Connecting to 127.0.0.1...
[14:12:20] *** Connected
[14:12:21] <PtokaX> This hub is running PtokaX DC Hub 0.3.5.2i2 Apr 17 2007 18:52:11 (UpTime: 0 days, 0 hours, 24 minutes)

[bastya_elvtars]

Please add this to the bugtracker.

[Stormbringer]

wow another fucking mods....
it's a copy and in more it destroys the hubs! nice
Hint: when you don't know how to code, just don't try to make a client, it sucks!

[CrazyGuy]

wow another fucking mods....
it's a copy and in more it destroys the hubs! nice
Hint: when you don't know how to code, just don't try to make a client, it sucks!

Hmm, If only it was this simply. ApexDC++ code does not show any issues regarding this

[PPK]

Hint: when you don't know how to code, just don't try to make a client, it sucks!

It don't sucks, it is fun
Anyway, we have bug, they have bugs... we have it already fixed and they have many work to do