Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mastodon.social/users/b0rk/statuses/109406564977270324">Julia Evans (b0rk@mastodon.social)'s status on Saturday, 26-Nov-2022 06:34:37 JST</a><a href="https://mastodon.social/@b0rk" title="b0rk@mastodon.social"><img src="https://gnusocial.jp/avatar/34761-48-20221121164832.webp" width="48" height="48" alt="Julia Evans" style="position: absolute; left: 0; top: 0;">Julia Evans</a></section><article><p>notes on reading error messages</p><p>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</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/681730#notice-1073743">In conversation</a><time datetime="2022-11-26T06:34:37+09:00" title="Saturday, 26-Nov-2022 06:34:37 JST">Saturday, 26-Nov-2022 06:34:37 JST</time> <span>from <span><a href="https://mastodon.social/@b0rk/109406564977270324" rel="external" title="Sent from mastodon.social via ActivityPub">mastodon.social</a></span></span><a href="https://mastodon.social/@b0rk/109406564977270324">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/383579">title: read the error messageError 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 unrelatedTricks 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&gt;&amp;1 | less`)note: if you don't include 2&gt;&amp;1 , less won't show you the error messages (just the program's output)</a></label><br><a href="https://files.mastodon.social/media_attachments/files/109/406/542/600/056/650/original/39ea1e70e797e066.png" rel="external">https://files.mastodon.social/media_attachments/files/109/406/542/600/056/650/original/39ea1e70e797e066.png</a></li></ol></footer></blockquote>

Corresponding Notice

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 conversationSaturday, 26-Nov-2022 06:34:37 JST from mastodon.socialpermalink
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

Public

Embed Notice

HTML Code

Corresponding Notice