Hi! 2009/11/16 Veit Jahns <[email protected]>: > 2009/11/15 Itamar Syn-Hershko <[email protected]>: >> Whatever the test looks like, as long as it compiles and reproduces the >> problem, it is a good test. Of course, a test being able to regenerate that >> exception internally instead of calling core functions manually is the best >> test. Try perhaps looking for such a test in the Java Lucene test suite. > > Opened a ticket > (http://sourceforge.net/tracker/?func=detail&aid=2898224&group_id=80013&atid=558446) > and added all changes so far. But I will also take a look into the > Java Lucene test suite.
I ported the MockRAMDirectory from the Java Lucene test suite and build a test case. But now I'm stuck. The test case fails, but not in the way I want him to fail: Executing "finishDocument(state)" (line 937 in index/DocumentsWriter.cpp) results in an exception, which is catched by the next _CLFINALLY macro. According to the code some statements later the method "addDeleteDocID(state->docID)" (line 956) to mark the document as deleted. But stepping through with gdb I don't get there. The next statement after the statements related to the mutex (line 942) is the catch statement in line 959. Has anyone an idea, why? Kind regards, Veit ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ CLucene-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clucene-developers
