Jamie McCracken wrote:
that should also save every debug message to
~/.local/share/tracker/tracker-indexer.log, it'd also be useful to see
the last messages before the crash.
A question: how do you compile all the code with -g for debugging?
In the past, configure had --enable-debug parameter
Jamie McCracken wrote:
Another potential crasher - unlike trunk get_file_content does no utf-8
validation and also if file is bigger than MAX_TEXT cuts it off which is
likely to not land on a valid utf-8 word break
This is true.
ideally do what trunk does and read file line by line so that
Jamie McCracken wrote:
Could we also reduce memory usage by not statically linking to the
private libs libtracker-common and libtracker-db?
Those libraries should not be available for public use. Before doing so,
each API would have to be:
a) Documented
b) Checked it needs to be public
c)
On Tue, 2008-09-02 at 12:14 +0100, Martyn Russell wrote:
Jamie McCracken wrote:
Another potential crasher - unlike trunk get_file_content does no utf-8
validation and also if file is bigger than MAX_TEXT cuts it off which is
likely to not land on a valid utf-8 word break
This is true.
On Tue, 2008-09-02 at 12:17 +0100, Martyn Russell wrote:
Jamie McCracken wrote:
Finding more performance issues
on an up to date indexed home directory, the next restart of trackerd
checks every single file to see if its up to date - why?
Because we redesigned the whole code base and
On Tue, 2008-09-02 at 12:23 +0100, Martyn Russell wrote:
Jamie McCracken wrote:
Could we also reduce memory usage by not statically linking to the
private libs libtracker-common and libtracker-db?
Those libraries should not be available for public use. Before doing so,
each API would have
