All kinds of things can go wrong with your shell scripts, but they don't have to. Let's look a some debugging tips that can help ensure your scripts run the way you intend. The first step in debugging ...
In my initial days of programming, I have spent hours trying to find the error in my code, and in the end, it might be something simple. You might have faced the same ...
Teeing all outputs to | tee -a log allows you to later search the outputs, but there are times when you want to search the outputs dumped to the terminal. Therefore it's critical to use a terminal ...
Last week's post provided some tips and tricks for debugging scripts. This week's provides some even better ones! In last week’s posting, I mentioned the -x and -v options that can be used on the ...
All programs use memory, even ones that do nothing. Memory misuse results in a good portion of fatal program errors, such as program termination and unexpected behavior. Memory is a device for ...
When trying to debug any corefx test in a Unix system the debugger is not able to load symbols. The only symbol that is correctly loaded is System.Private.Corelib one. All the symbols are present and ...
In a typical work week, a Unix systems administrator is likely to have at least one small mystery to solve — one “huh?”, one “that doesn’t make any sense” or one “I’ve never seen this before”. Most of ...
In my college computer science lab, two eternal debates flourished during breaks from long nights of coding and debugging: “emacs versus vi?” and “what is the best programming language?” Later, as I ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results