Public
- Public
- Network
- Groups
- Featured
- Popular
- People

Conversation

Notices

Embed this notice
Julia Evans (b0rk@mastodon.social)'s status on Saturday, 26-Nov-2022 06:34:37 JST Julia Evans

notes on reading error messages
I'm wondering if there are more tips I should include here -- for example "remove the parts specific to your program when Googling the error" feel too obvious to me
In conversation Saturday, 26-Nov-2022 06:34:37 JST from mastodon.social permalink
Attachments
1. 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)
  https://files.mastodon.social/media_attachments/files/109/406/542/600/056/650/original/39ea1e70e797e066.png

Feeds