Skip to content
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

Segfault caused by typo in query: #5

Closed
Buchhold opened this issue Jan 20, 2017 · 0 comments
Closed

Segfault caused by typo in query: #5

Buchhold opened this issue Jan 20, 2017 · 0 comments
Assignees
Labels

Comments

@Buchhold
Copy link
Member

Buchhold commented Jan 20, 2017

Happened for a query for politicians who had an audience with the pope on the clueweb+freebase dataset. Would probably happen for all queries that make words look like variables.

PREFIX fb: <http://rdf.freebase.com/ns/> 
SELECT ?pol ?lead TEXT(?c) SCORE(?c) WHERE { 
  ?pol fb:people.person.profession fb:m.0fj9f . 
  ?pol <in-context> ?c . 
  ?c <in-context> audience .
  ?lead <in-context> ?c . 
  ?lead fb:people.person.profession fb:m.05hmbp4 . 
  FILTER(?pol != ?lead) 
} ORDER BY DESC(SCORE(?c))

With typo ?audience instead of audience and missing selects I can produce a segfault:

PREFIX fb: <http://rdf.freebase.com/ns/> 
SELECT ?pol ?lead  WHERE { 
  ?pol fb:people.person.profession fb:m.0fj9f . 
  ?pol <in-context> ?c . 
  ?c <in-context> ?audience .
  ?lead <in-context> ?c . 
  ?lead fb:people.person.profession fb:m.05hmbp4 . 
  FILTER(?pol != ?lead) 
} 

Fix this after paper dealine!

@Buchhold Buchhold changed the title Segfault cause by typo in query: Segfault caused by typo in query: Jan 20, 2017
@Buchhold Buchhold added the bug label Jan 20, 2017
@Buchhold Buchhold self-assigned this Jan 20, 2017
@Buchhold Buchhold closed this as completed Jun 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant