similar to: Segmentation Faults

Displaying 20 results from an estimated 10000 matches similar to: "Segmentation Faults"

2006 Apr 03
6
Installing Ferret locally on TextDrive
I would like to give the 0.9.0 version of Ferret a try on my application hosted on TextDrive. I am currently running on the 0.3.2 version there. Does anyone have any tips on installing it locally there? I know just enough about Ruby gems to get by... but I am thinking it could be as easy as passing a -i flag to specify the install location for ferret. Then, the only thing I am not sure about
2006 Aug 04
5
A couple of ferret 0.9.4 exceptions
Hi Dave, I am using ferret at my site http://gifthat.com and I just had a few exceptions pop up. I don''t have a way to reproduce them, but my site just was listed on lifehacker.com and these issues have popped up under multiple concurrent users (only twice though which I think isn''t too bad). I am using two lighttpd instances both with read/write access to the index: 1) Error
2006 May 30
3
Rebuild Indexes Issue
Hi, I have some code to rebuild my ferret indexes but occasionally some stale documents remain in the index even after rebuilding. The only way I could find around this is to manually delete the index files from the filesystem. Here is the code I have for rebuilding one of my indexes for Gifts: # delete existing entries INDEX.size.times {|i| INDEX.delete(i)} gifts =
2006 May 01
12
pagination in acts_as_ferret
I''m just wondering where I would put the pagination for search results when using "acts_as_ferret". At the moment my search code is.. def search @query = params[:query] || '''' unless @query.blank? @results = Tutorial.find_by_contents @query end end Cheers SchmakO -- Posted via http://www.ruby-forum.com/.
2006 Aug 15
5
Ferret Segmentation Faults
Hi, I am getting a number of segmentation faults using Ferret 0.9.5, Fedora Core 5 and Ruby 1.8.4 I installed it with the recommended gem install ferret and example segmentation fault creation line would be as follows: @records = FerretConfig::INDEX.search("address_line_2:\"Dumbarton\"") I am also using acts_as_ferret and rails 1.15 but think this is an issue with
2006 Jun 29
13
find_by_contents not returning SearchResults?
The acts_as_ferret documentation says find_by_content returns an instance of SearchResults, but I see this error when I try to use the results. undefined method `total_hits'' for []:Array Here is the link to the documentation: http://projects.jkraemer.net/acts_as_ferret/rdoc/classes/FerretMixin/Acts/ARFerret/ClassMethods.html#M000010 But here is the actual code: result =
2006 Oct 16
3
seg faults and problems with new version
Hi all, first off, it''s 2AM and I''m not thinking properly, so please forgive me if this one''s easy, but I just need to get this going. First problem, using 0.9.6 on all of our development machines, works great, then we move it to a server running x86_64 linux and it segfaults as soon as it tries to create an Index. I''ve tried rebuilding with different
2006 Aug 14
3
Ferret 0.9.5
Hi, I was wondering if the latest version of acts_as_ferret (0.2.2) that is listed on http://projects.jkraemer.net/acts_as_ferret/ is compatible with the latest version of Ferret 0.9.5. I noticed that the website above stated that it was supposed to work with 0.9.4, but I didn''t see anything about 0.9.5. Thanks, Aaron -- Posted via http://www.ruby-forum.com/.
2006 Jul 10
2
acts_as_ferret 0.2.2
Hi all, I just tagged acts_as_ferret 0.2.2 as the current stable version, so get it while it''s hot ;-) new features: - added support for the multiple models/single index approach. - find out the total number of search results by calling total_hits on the array returned by find_by_contents. fixes: - trac tickets #20 (find_by_contents breaks ferret sorting) and #24
2006 Jul 11
5
Ferret Wiki Spam - Solutions Anyone?
Hi All, As some of you may have noticed, the Ferret Wiki has been getting spammed like crazy. And I haven''t been able to do anything about it because I just don''t have the time. I''m getting pretty close to releasing 0.10.0 which has been the major draw on my time for the last couple of months so I''m going to have some time to look into this soon. I was
2008 Apr 04
1
Bug Report: Segmentation Fault when indexing with a specific set of FieldInfos.
I''m submitting this through the mailing list because Trac won''t let me use its bug report form... Is there some more appropriate way of submitting bugs if Trac doesn''t work? This is the Trac error message: 500 Internal Server Error (Submission rejected as potential spam (IP 127.0.0.1 blacklisted by bsb.empty.us, sc.surbl.org, Maximum number of posts per hour for this
2007 Jan 21
4
could not install in WinXP
Directory of C:\search_app 01/21/2007 19:37 <DIR> . 01/21/2007 19:37 <DIR> .. 01/21/2007 19:36 427 008 ferret-0.10.13.gem 01/21/2007 19:07 148 992 rdig-0.3.4.gem 2 File(s) 576 000 bytes 2 Dir(s) 45 135 982 592 bytes free C:\search_app>gem install ferret Building native extensions. This could
2007 Apr 19
7
Lock errors and segfaults
Greetings, I''ve been using ferret with great results now for a while, but in the last week, I''ve been running into some issues. I will occasionally see this message: Exception Message: Lock Error occured at <except.c>:103 in xpop_context Error occured in index.c:5368 - iw_open Couldn''t obtain write lock when opening IndexWriter Which is accompanied by
2007 Jan 11
1
Ferret Locking issues
Dave and all, I run a medium RoR app using Ferret and acts_as_ferret. I get a lot of lock errors. Not always but around 5% of all searches (aspecially during peak periods). Here are the messages I get: A NameError occurred in szukaj#index: uninitialized constant Ferret::Index::Index::LockError [RAILS_ROOT]/vendor/rails/activesupport/lib/active_support/dependencies.rb:478:in
2006 Nov 01
8
aaf and stop words; query parser
I''ve been trying to implement acts_as_ferret in my latest project and ran into a snag. If I do a search for ''auditor state'' then the search works perfectly. If I include a stop word, as in ''auditor of state'', then I get no results. I''d prefer not to set stop words to nil and index everything. The solution, that I have yet to attempt, is to use
2007 Jan 17
1
ferret and mongrel
Dear all, Does anybody know if there''s problem with ferret running with mongrel ? I got unpredictable segfaults. Everything works well with fastcgi instead of mongrel. I use ruby 1.8.5, apache 2, mod proxy, mongrel 0.3.13.4, ferret 0.10.13 and rails 1.1.6 Thanks, Johan Johan Duflost Analyst Programmer Belgian Biodiversity Platform ( http://www.biodiversity.be) Belgian Federal
2006 Nov 22
2
crash while retrieving term vectors
This program reliably crashes for me (usually a segfault): require ''rubygems'' require ''ferret'' reader=Ferret::Index::IndexReader.new ARGV fields=reader.field_infos.fields reader.max_doc.times{|n| fields.each{|field| reader.term_vector(n,field) } unless reader.deleted?(n) print "."; STDOUT.flush } As you can see, it just goes through
2006 Oct 25
4
Search result inconsistencies due to indexing
I seem to be having problems with getting my searcher to be consistent while indexing. I am running the latest version of ferret (0.10.13) and I am using the Searchable plugin. Currently the way it indexes is by using a callback in the model of either after_update or after_create to index the fields that I have setup to be indexed. Right now I update the index about once every 4 or 5
2006 Dec 08
6
QueryParser Exception Handling Problem
According to the following link: http://ferret.davebalmain.com/api/classes/Ferret/QueryParser.html :handle_parser_errors => true is enabled by default and seems to be in acts_as_ferret in class_methods.rb of the plugin. However, when I pass a special character as a query (e.g., !, -, <, >, etc) it throws an error and pukes. -- snip -- Error occured in src/q_parser.y:279 - yyerror
2006 Apr 15
1
Segmentation Faults with Fuzzy Queries
There are certain queries that I can execute that will cause a completely repeatable segmentation fault at the point where the search or search_each leaves my control and goes into the ferret libraries. I tried deleting my indexes and recreating them, and even so the exact same queries seg fault repeatedly after. Usually a one character change will make them succeed. Changing away from a