Doesn't play nicely with node-webkit about node-geoip

[bluesmoon]

can you trace through the code to see what's happening?

[isdampe]

I'll have a deeper look later, it's a little hard with node-webkit because it seems to be quite selective what is showed when debugging

[bluesmoon]

throw in some console.log statements in the geoip code

[isdampe]

Even then node-webkit doesn't seem to log all existing console.log statements (maybe due to the fact i tries to reroute the io stream?)

So far I've determined that the paths to the data files are still correct, haven't been relatively incorrect.

Is there a minimum version of node required?

EDIT
Sorry just realised there was. Node-webkit has been built with

node-webkit v0.10.5
node.js v0.11.13-pre

So that shouldn't be an issue.

[isdampe]

It appears that when running under node-webkit, around line 330ish, these values are different:

cache4.lastLine = (datSize / cache4.recordSize) - 1;
cache4.lastIP = cache4.mainBuffer.readUInt32BE((cache4.lastLine * cache4.recordSize) + 4);
cache4.firstIP = cache4.mainBuffer.readUInt32BE(0);
console.log(cache4.lastIP);

Terminal based node result shows 3758096383, when in node-webkit, it shows -536870913

[bluesmoon]

looks like a difference in how the two types of node read in files from
disk. I know we did have problems with older versions of node (prior to
0.10), so could it be that node-webkit is based off an older version?

[ar2rsawseen]

If issue is still valid, please reopen