search for: logcall_void

HI, Many functions in xapian can be traced when they are called using LOGCALL_CTOR/LOGCALL_VOID/... and I want to output the debug information. So, I first install xapian and enable log, using commands as follow ``` cd xapian-core-1.4.5 # xapian source code downloaded ./configure --enable-log=yes --enable-assertions=yes make sudo make install ``` But there isn't any debug information whe...

On 9 Jun 2018, at 07:37, 张少华 <xiangqianzsh at 163.com> wrote: > Many functions in xapian can be traced when they are called using LOGCALL_CTOR/LOGCALL_VOID/... and I want to output the debug information. In xapian-core/HACKING in the source code there's a section on this. As well as pass --enable-log to configure, you also need to: * set XAPIAN_DEBUG_LOG to be the path to a file that you would like debugging output to be appended to, or to t...

Hi, I have read the concurrency webpage from the Xapian documentation: http://getting-started-with-xapian.readthedocs.io/en/latest/concepts/concurrency.html But it is still not clear to me how to ensure thread-safety when using libxapian (C++ API). Usually when doing multi-threading many threads can read the same variable concurrently without locking provided none of the threads modifies the

...+#include <iostream> + #include "esetinternal.h" #include "xapian/enquire.h" @@ -142,6 +145,7 @@ const Xapian::Internal::ExpandWeight & eweight, Xapian::weight min_wt) { + cout << "In Eset::Internal::expand" << endl; LOGCALL_VOID(EXPAND, "ESet::Internal::expand", max_esize | db | rset | edecider | eweight); // These two cases are handled by our caller. Assert(max_esize); @@ -168,7 +172,11 @@ string term = tree->get_termname(); // If there's an ExpandDecider, see if it accepts the term. - if...

My code is not on Github. I am using the tarball as of now. The following it the error that occurred: http://pastebin.com/cVJrjUZX On Sun, Apr 13, 2014 at 8:16 PM, James Aylett <james-xapian at tartarus.org>wrote: > On 13 Apr 2014, at 15:37, Pallavi Gudipati <pallavigudipati at gmail.com> > wrote: > > > A linker error is encountered even after following the above