Search Results for "print"

Do you ever use print() or log() to debug your code? Of course you do. IceCream, or ic for short, makes print debugging a little sweeter. With arguments, ic() inspects itself and prints both its own arguments and the values of those arguments. Just give ic() a variable or expression and you're done. ic() returns its argument(s), so ic() can easily be inserted into pre-existing code.

q is a better way to do print statement debugging. For best results, dedicate a terminal to tailing $TMPDIR/q while you work. You also can simply tail -f $TMPDIR/q, but it's highly recommended to use the provided commands. Type q.Q instead of fmt.Printf and your variables will be printed like the provided example. Faster to type, pretty-printed vars and expressions.

PySnooper is a simple yet powerful Python debugging utility. Just add a @pysnooper.snoop() decorator, and it logs line-by-line execution with timestamps and local variable tracking—saving you from inserting print() statements manually.

...It's not a replacement for a full-fledged debugger, but it's pretty close and will be useful in 90% of the cases. I use it as my sole debugger (in rare cases I reach for print statements).

For C (and CPP obviously): Include a fast and tiny RAM-tracing feature for Real-Time (RT) debugging purposes. >> ONLY FOR DEBUGGING << Very much faster than printf-debugging, which may result in unforseen results in an RT environement.

pyringe is a powerful Python process “syringe” that attaches to a running interpreter and lets you introspect—and even execute code inside—that live process. It blends debugger-style attachment (via gdb/ptrace techniques) with Python-aware helpers so you can inspect threads, frames, locals, and heap objects without restarting the target. This is invaluable for post-mortem diagnosis of production daemons where reproducing a bug in a dev shell is impractical. pyringe can inject arbitrary...

A logging utility for C++ applications. It supports levels of escalation and safety within multiple threads. Optional "ghost" output for specific messages to stream, in order to log and print to screen at the same time.

A light-weight tool to detect the memory leak in C++ Program under Mac environment. It will trace the memory allocation stack and print it out when your program exit.

JTail is a simply multiplatform application, which show text files content especially LOG FILES. This application is a thread, which non-stop reads the file content and print what lines was added to the end file.