cbab

8 ms·

1.
by cbab 11y ago
Yup, basically Chrome is using an inverted flame graph (See [1] for additional infos and tools). [1] - https://github.com/brendangregg/FlameGraph
2.
Tracing bare-metal systems: a multi-core story(lttng.org)
47 points by cbab 12y ago|0 comments
3.
by cbab 12y ago
A great book on the subject is "The Art of Debugging with GDB, DDD, and Eclipse" [1]. [1] - http://www.nostarch.com/debugging.htm
4.
by cbab 12y ago
Very nice concept. Reminds me a lot of my TI-83 graph calculator days with a small dose of Scorched Earth :).
5.
by cbab 12y ago
Thanks for reporting your issues on Fedora. 4) We will definitely fix that omission. 5a) liburcu is a dependency of the lttng-ust and lttng-tools. The dependency should be accounted for in the respective Fedora packages. 6) Yes please submi
6.
by cbab 12y ago
You can also find all the presentations/publications that we did through the years here [1]. [1] - http://lttng.org/publications/
7.
by cbab 12y ago
Thanks, we worked quite hard on this new redesign! edit: Yes, EfficiOS [1] is the open source business behind the LTTng project :). [1] - https://www.efficios.com/
8.
by cbab 12y ago
The Userspace RCU [1] library might also be interesting for wait-free linked lists and other RCU aware data structures. [1] - http://lttng.org/urcu/
9.
by cbab 12y ago
One of the main technical reason I would say is that CeroWRT has the CoDel[1] queue management enabled by default. See also [2]. [1] - http://www.bufferbloat.net/projects/codel/wiki [2] - https://www.bu
10.
by cbab 12y ago
Yes indeed. Encouraging open source contribution, validating that he/she can get stuff done and evaluate culture fit. Win-win-win.
11.
by cbab 12y ago
On recent C++ projects, I used the TAP [0] test format. It's quite minimalistic and does the job. Debugging tools have improved quite a bit. I suggest you take a look at asan [1] for memory related errors. Also, tsan [2] looks very pro
12.
by cbab 12y ago
I respectfully disagree with this. Ignoring return values is _not_ good practice. It is a slippery slope to bad software. By catching these memory errors, a program has the chance to properly teardown and report a message to the user instea
13.
by cbab 13y ago
Absolutely! Codebases in "franglais" are terrible. Also, when documenting such codebases, I cringe whenever I see public APIs with mixed language members.
14.
by cbab 13y ago
or LTTng with both kernel and userspace tracers http://lttng.org Disclaimer: LTTng developer :)