“Many times I have come across seemingly hopeless situations
where a program when compiled and installed in GNU/Linux just fails
to run. In such situations after I have tried every trick in the
book like searching on the net and posting questions to Linux
forums, and still failed to resolve the problem, I turn to the last
resort which is trace the output of the misbehaving program.
Tracing the output of a program throws up a lot of data which is
not usually available when the program is run normally. And in many
instances, sifting through this volume of data has proved fruitful
in pin pointing the cause of error…”
Related Story:
OSWeekly: How
System Calls Work in Linux?(Apr 11, 2006)
Web Webster has more than 20 years of writing and editorial experience in the tech sector. He’s written and edited news, demand generation, user-focused, and thought leadership content for business software solutions, consumer tech, and Linux Today, he edits and writes for a portfolio of tech industry news and analysis websites including webopedia.com, and DatabaseJournal.com.
LinuxToday is a trusted, contributor-driven news resource supporting all types of Linux users. Our thriving international community engages with us through social media and frequent content contributions aimed at solving problems ranging from personal computing to enterprise-level IT operations. LinuxToday serves as a home for a community that struggles to find comparable information elsewhere on the web.
Property of TechnologyAdvice. © 2025 TechnologyAdvice. All Rights Reserved
Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.