-
Notifications
You must be signed in to change notification settings - Fork 2
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! #87
Comments
This is an error in DB XML itself - I can also reproduce it using the 'dbxml' command-line tool. I'll try to see if there is a simple fix and report it upstream. |
Reported upstream: https://forums.oracle.com/forums/thread.jspa?threadID=2385891&tstart=0 I also made a workaround (in DB XML) that solves the segfault. But let's wait and see what the upstream developers say... |
I have applied the workaround to DBXML in our Ubuntu and Windows builds, and will also do this for the Mac version (which is still blocked by #56). Let's keep this bug open until we hear from upstream. |
We still have this bug in our Mac version, but now that we have a Homebrew repo, we could add the DB XML patch there. |
Seems to work out of the box in the new DB XML (6.0.17)! |
bij de volgende query voor het Lassy corpus /net/corpora/Lassy/lassy.dact
//node[@cat='conj' and count(node[@rel='crd'])=1 and count(node[@rel='cnj'])=2 and number(@begin)=number(@EnD)-3 and node[@rel='cnj']/@pt != node[@rel='cnj']/@pt]
The text was updated successfully, but these errors were encountered: