| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
There exists a race condition that can lead to a segfault. Thanks
go to vbernetr, who performed the analysis and provided patch, which
I only tweaked a very little bit.
|
| | |
| |
| |
| |
| |
| | |
This enables us to use more efficient calling conventions and
also helps us keep the on-disk structure of a msg object more
consistent in future releases.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
cleaned up previous code and redid it in a way that makes
it much easier to extend it
also added a new macro DBGPRINTF which is a performance-optimzed
version of dbgprintf
|
| |/
|
|
|
|
|
| |
There was a wrong order of mutex lock operations. It is hard to
believe that really caused problems, but in theory it could and with
threading we often see that theory becomes practice if something is only
used long enough on a fast enough machine with enough CPUs ;)
|
|
|
there are still some files left which could go into the
runtime, but I think we will delete most of them once we
are done with the full modularization.
|
