Explore >> Select a destination
|
You are here 
|
isocpp.org | ||
| | | | |
therealmjp.github.io
|
|
| | | | | Overall Approach Setting Up The Print Buffer The "Magic" Debug Info Buffer Dealing With The String Problem A Cursed Path Packing It All Into A Buffer Reading Back On The CPU Going Beyond Printf CR LF Unless you're fortunate enough to to be working exclusively in Cuda, debugging GPU shaders is still very much "not great" in the year 2024. Tools like RenderDoc and PIX are amazing and do provide the ability to step through a shader and inspect variables, but they're fundamentally tied to a "capture" workflow. | |
| | | | |
0xd34df00d.me
|
|
| | | | | ||
| | | | |
brevzin.github.io
|
|
| | | | | ||
| | | | |
eyakubovich.github.io
|
|
| | | It's a simple task -- you want iterate over all the lines in a file and perform an action on each one. In Python it's as simple as:for line in open("somefile.txt"): print lineHow about C++11. How hard can it be? This stackoverflow post gives us a starting point. We... | ||
