VS2010 + Perl 5.14 = Zone.exe crash
 

Hello,

here is a problem, which I will kind of step through, its a little messy: (I can provide more detailed dumps if need-be, im hoping this is a PEBKAC issue)

I have scoured the forums as well as google. I am too dumb to figure it out myself - or I haven't found the answer yet.

Here is the problem:
I installed vs2010
downloaded mysql 5.1 zip archive (just for the includes for vs)
perl 5.14
zlib

I checked out the code with visualSVN within vs2010 - great
setup the directories to point to mysql/zlib/perl - great

compile as 32 bit releaseBOTS
succesfully compile 5 files

then i go to run it
everything good then zone.exe keeps crashing nonstop without ever succesfully loading.

nothing in log files, so i recompile as debugbots
log files indicate that zone.exe is failing when trying to load quests, so it doesn't initialize.

I say ok fine, so I rename quests dir to see if it is a specific quest - no, it is still failing

I am stuck now

I even found dependancy walker (Great program btw), and none of the perl 5.14 dependancies seem to be looking for an x64 file so that (i think) is ok.

I suppose the next part is to learn some c++ - and run the server from the host instead of a vm, and attach a debugger to it, come back here and complain some more.

I can get it all working 100% if i use vs 2008, and an older perl / mysql, but I wanted to benefit from the reduced bugs (supposedly) of the newer perl and vs2010 optimizations for the server.

The server configuration itself is fine, i can load to char select even. And it was working fine before with the 2098 release

I am seeing some posts suggesting that perl 5.14 only works with x64? Then some people claiming they got it working with x86, so did those people who compiled successfully (as I did) actually get a server up and running with x86 version of perl 5.14?

IMO, save yourself the hassle and use VS 2008 and Perl 5.12. VS 2010 doesn't generate significantly different code than 2008, and I doubt you'd see a difference in Perl versions. I haven't seen a problem posted yet that was Perl version specific and due to a Perl bug.

I'm having the same issue. What did you do? get it resolved?


Do we really have to go back to 5.10/2008?

I installed vs2008 w 5.12 perl

sadface

it works but i wanted that extra few % of quality that i dont even need

Eventually i will do it all w x64. i just dont have time

x64 mysql perl compile w perl 5.14 supposedly works.

I need to do research into whether i should do it. im running a number of servers for people using a x64 host and a bunchof x86 client VMs. i need to know if a x64 client makes a diff at all. shrug