Segmentation fault in data_objects on new hosting (Nginx+Passenger) about do

[godfat]

I am running ruby 2.0.0p195 (2013-05-14 revision 40734) [x86_64-darwin12.2.1] and seeing a segfault after doing a select with ALTER TABLE with postgres as well.

But it looks to me it's more a Ruby bug since it segfaulted at lines in Ruby code instead of native code. However it's actually hard to tell. I don't yet have time to figure out what's going on, but want to let people know we have similar issues. (though it might not be related)

[dbussink]

Could any one of you create a small repro for this to reproduce the problem? Ideally just a script with no dependencies except for DataObjects itself. I'm sure it would be fairly easy to fix then.

[crantok]

@dbussink I'll try to do that tomorrow morning (I'm in the UK) and post a link here. This is my first DataMapper app and I'm relatively new to Ruby. If I get stuck then I'll mention that here too.

[godfat]

Here it is. https://gist.github.com/godfat/5626115
So it looks like it crashed at execute_reader which is a C function.

[godfat]

Could it be a postgres change? I am using psql --version psql (PostgreSQL) 9.2.4

[crantok]

I've uploaded a script that's based on godfat's. https://gist.github.com/crantok/5626645

One thing I forgot:
Server version: 5.5.30-30.1 Percona Server (GPL), Release rel30.1, Revision 465

[dbussink]

@crantok Looks like your issue is a different one from @godfat, they don't seem to be related. I've managed to reproduce the issue of @godfat, but the one @crantok reported seems to run fine for me.

[crantok]

That's a pity. Any idea what my next step should be? I wonder whether it's worth pointing my host's support at this thread.

[dbussink]

I don't know if it's possible to set up a machine somewhere that shows this problem? If you could get this crash reproduced in for example an isolated virtual machine that I could get access to, that would be great. That's probably the easiest way to get the information needed to fix this issue.

[crantok]

Providing a VM is beyond my abilities. I've raised a ticket with my host to see if they can help in this regard.

[crantok]

I've found out that there was a problem with the gem installation on my hosting account. Reinstallation killed the problem so my original issue was a phantom. I haven't closed the issue in case you still need it open for the postgres segfault.

[dbussink]

Ah, I'm closing it then, since the postgres segfault was fixed.