Invalid size for RecipeDetails Request

[gaeorn]

linux doesn't like to actually compile for 32bit, so you are having 32bit vs 64bit issues. compile on the 32bit box and copy the executable over to the 32bit box and try that.

in any case, i'll try to take a look at this later. something probably needs to be changed from int to int32 or uint to uint32.

[huntersan9x]

Well, I copied zone, eqlaunch, libEMuShareMem.so and after an unsuccessful start, also libmysqlclient.so.* from my 32 bit box to the 64 bit box and it shows the items as intended. Is there anything more I can do to help with making this work on 64 bit?

[gaeorn]

I have the information needed. I just need to get around to fixing it

I'll see if I can get to this sometime this week.

[c0ncrete]

I ran into this problem as well using a 64-bit Ubuntu system.

I resolved it by changing unsigned long to unsigned int (uint32) in the following:
Client::Handle_OP_RecipeDetails()
Client::SendTradeskillDetails()

It looks to me like the packet the client is sent is constructed in part using the bit length of unsigned long. From what I understand, this is the same on both 32-bit and 64-bit Windows systems, but can be larger on some other systems.

There are plenty of other areas in the source that use unsigned long, but I haven't run across any other issues just yet. I can't wrap my head around why unsigned long is used at all instead of unsigned int for the sake of portability.

DISCLAIMER: I'm no computer scientist. I just use Google to feel my way around any given subject. Reading is fun...

[provocating]

Originally Posted by c0ncrete

I ran into this problem as well using a 64-bit Ubuntu system.

I resolved it by changing unsigned long to unsigned int (uint32) in the following:
Client::Handle_OP_RecipeDetails()
Client::SendTradeskillDetails()

It looks to me like the packet the client is sent is constructed in part using the bit length of unsigned long. From what I understand, this is the same on both 32-bit and 64-bit Windows systems, but can be larger on some other systems.

There are plenty of other areas in the source that use unsigned long, but I haven't run across any other issues just yet. I can't wrap my head around why unsigned long is used at all instead of unsigned int for the sake of portability.

DISCLAIMER: I'm no computer scientist. I just use Google to feel my way around any given subject. Reading is fun...

I am hitching a ride on the topic since I have the same issue. Did this fix it for good on your server?

[c0ncrete]

the server no longer exists (redemption), but it solved the issue. sent pm.