• Public

  • Public
  • Network
  • Groups
  • Featured
  • Popular
  • People

title: read the error message Error messages are a goldmine of information, but they can be very annoying to read: abstract picture of an error message: lots of squiggles - giant 50 line stack trace full of impenetrable jargon - can even be misleading , like "permission denied" sometimes means "doesn't exist" - often seems totally to your bug unrelated Tricks to extract information from giant error messages: 1. SCROLL UP! Usually the first line is a summary 2. On the command line, pipe it to `less` so that you can scroll/search it ( `./my_program 2>&1 | less`) note: if you don't include 2>&1 , less won't show you the error messages (just the program's output)