| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
| |
output
Serializing the data is the expensive part, so we want to completely
avoid that for the noisier part if we're not going to use it.
Additionally we're now using a stringbuilder for the debugarea to try to
further improve the situation with temporary memory allocations.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
To have hierarchical debug output we have to pass around something at
run-time, there is no reasonable alternative. Log::Context provides the
identifier to do just that and largely replaces the debug component
idea.
|
| |
|
|
|
| |
The sinksh command allows to easily turn tracing for certain areas on
or off.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of a single #define as debug area the new system allows for an
identifier for each debug message with the structure component.area.
The component is a dot separated identifier of the runtime component,
such as the process or the plugin.
The area is the code component, and can be as such defined at
compiletime.
The idea of this system is that it becomes possible to i.e. look at the
output of all messages in the query subsystem of a specific resource
(something that happens in the client process, but in the
resource-specific subcomponent).
The new macros are supposed to be less likely to clash with other names,
hence the new names.
|
| | |
|
| |
|
|
| |
clang-format -i */**{.cpp,.h}
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
qputenv only modifies the env of the current process,
so akonadish didn't work at all to change the settings.
We might have to do some performance optimizations at some point,
but for the time being this works.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This cuts the exportet symbols from 12k to 2k and the library size from
16Mb to 14Mb, which isn't great but still an improvement.
About 30% of the symbols are coming from the Store:: interface.
nm -C -D /work/install/lib64/libsinkcommon.so.0.1
|
| |
|
|
| |
(except for documentation).
|
| | |
|
| |
|
|
|
|
| |
Unittests can set the level themselves (so i.e. benchmarks don't print
a shitload of messages), while in normal operation we can set it from
the environment. There's no override currently, but first things first.
|
| | |
|
| |
|
|
| |
With Storage::Error. Perhaps turn to akLog, akError, ...?
|
| |
|
