[BUG] Segmentation fault >= 1.9.3

[igravious]

I'm not going to paste the entire trace. RDF::Raptor 1.2.1 requires FFI >= 1.9.3 but that causes a segmentation fault. Pinning FFI to < 1.9.3 allows RDF::Raptor 1.0.1 to be used.

I'm not sure if the fault is with FFI or RDF::Raptor so I'm posting to both.

[dwbutler]

Can you please paste the trace into a gist?

@gkellogg Any idea why the FFI dependency was pinned to >= 1.9.3?

[gkellogg]

Typically, when a release is made, the gem versions are set to ~> and >=, although in the case of rdf-raptor, the ~> was never set. If there's a particular version that should be used, I'd suggest either = xxx or ~> xxx.

[igravious]

Here be the gist: https://gist.github.com/igravious/a0e1c0f4387625938a3d

[dwbutler]

@gkellogg I was interested to know why FFI was pinned to >= 1.9.x, rather than >= 1.0.x as before. Was there a bug fix or new feature you were picking up? I'm looking at d864560

@igravious Do you have a reliable way to reproduce this issue? It looks like the issue occurs during parsing XML. I've seen libraptor segfault when provided with data that's not encoded in a valid way.

[gkellogg]

On Mar 27, 2015, at 2:18 AM, David Butler [email protected] wrote:

@gkellogg I was interested to know why FFI was pinned to >= 1.9.x, rather than >= 1.0.x as before. Was there a bug fix or new feature you were picking up? I'm looking at d864560

Looks like a botched attempt to correct an issue with a different setting for rbx in the Gemfile. Note that >= 1.0.x doesn't pin a version, and on installation would use the latest gem available. Use ~> to ensure an upper bound on the gem version used. Likely, when I was doing the update, my Gemfile.lock had used 1.9.3 and that's why it was set to that particular version.
@igravious Do you have a reliable way to reproduce this issue? It looks like the issue occurs during parsing XML. I've seen libraptor segfault when provided with data that's not encoded in a valid way.

—
Reply to this email directly or view it on GitHub.

[tduehr]

There are many reasons to use 1.9.3 as the lowest version. Mostly, they all involve 1.9.2 not working right and several bugs and packaging issues being corrected since 1.9.3. If you're not on windows I recommend the current version 1.9.8.

This looks like it may be an issue in rdf-raptor but I need example code before I can be sure.

[dwbutler]

@tduehr Thanks for the info!

I'm also pretty sure it's an issue with RDF::Raptor rather than FFI.