From dfe60872d2e853709e09c121cfd6ab83e1dff52a Mon Sep 17 00:00:00 2001 From: Marko Ivanovich Date: Sun, 5 Dec 2021 13:50:11 +0300 Subject: [PATCH] Update README to mention solution. --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 83173a3..c17bce8 100644 --- a/README.md +++ b/README.md @@ -24,7 +24,7 @@ call) with a Python 3.x interpreter. ## Libraries/Wrappers | Language | Link | -| ----------- | ----------- +| ----------- | ----------- | Java | JCoz: https://github.com/Decave/JCoz| | Go | Cozgo: https://github.com/urjitbhatia/cozgo| @@ -61,6 +61,10 @@ To run your program with coz, you will need to build it with debug information. Once you have your program built with debug information, you can run it with coz using the command `coz run {coz options} --- {program name and arguments}`. But, to produce a useful profile you need to decide which part(s) of the application you want to speed up by specifying one or more progress points. +If your program uses `jemalloc`, `tcmalloc`, or any other allocation algorithm, +and it crashes or deadlocks during profiling, try passing `--with-alloc-shims` +option to coz. + ### Profiling Modes Coz departs from conventional profiling by making it possible to view the effect of optimizations on both throughput and latency. To profile throughput, you must specify a progress point. To profile latency, you must specify a pair of progress points.