-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault on triples insertion #56
Comments
With a different use‑case, I got a crash with this additional message:
|
For the one above, I could figure the cause. That’s because I did this from another terminal:
Instead of:
|
It is not immediately obvious to me why RedStore is crashing. What you are attempting to do looks reasonable. It is useful to check to see if this is a RedStore problem or a Redland problem but attempting to do the same thing using Be warned that there also hasn't been a release of Redland since 2013. nick. |
One segmentation fault was preceded by an interesting message:
The preceding warning message may be worth to note. — Edit — More than one time, it was always there, I just have not noticed before (shy). |
I can’t reproduce the crash with
… works It fails with RedStore only and RedStore does not crash if I use May be it expects something somewhere, tries to access this non‑existing thing and then segfault. |
README.md explicitly states that "You can use any of the Redland Storage Modules that supports contexts" |
I started RedStore using:
Then in the web interface I tried to insert some test triples:
… using Turtle for the syntax and “bar” for the base URI. When I clicked “Send”, the browser told me the connexion was reinitialised, and in the terminal within which I started RedStore, there was this message:
This is not random, this always happens each time I retry the same. I’ve set
ulimit -c
tounlimited
to get a core‑dump file, but it’s big (620K) so I don’t know if it’s OK to attach it here.If this can help,
uname -a
says:The text was updated successfully, but these errors were encountered: