From: Joshua Ballanco <jballanc@...>
Date: 2013-07-23T04:56:13+09:00
Subject: [ruby-core:56109] Re: [CommonRuby - Feature #8661][Open] Add option to print backstrace in reverse order(stack frames first & error last)

--089e0160ca3c6c6d0d04e21f11db
Content-Type: text/plain; charset=UTF-8

You can already accomplish something like this yourself:

    begin
      raise "Hello!"
    rescue Exception => e
      puts e.backtrace.reverse.join("\n")
      puts e.message
    end

Simple!


On Sat, Jul 20, 2013 at 11:20 PM, gary4gar (Gaurish Sharma) <
gary4gar@gmail.com> wrote:

>
> Issue #8661 has been reported by gary4gar (Gaurish Sharma).
>
> ----------------------------------------
> Feature #8661: Add option to print backstrace in reverse order(stack
> frames first & error last)
> https://bugs.ruby-lang.org/issues/8661
>
> Author: gary4gar (Gaurish Sharma)
> Status: Open
> Priority: Normal
> Assignee:
> Category:
> Target version:
>
>
> Currently the way ruby prints the backtrace is that the error comes first
> & then the stack frames. like this
>
>   Main Error Message
> stack frame 1
> stack frame 2
> stack frame 3
> .....
>
>  this is perfectly fine provided
>
> 1. Backstraces are short, so fits in terminal.hence, no need to scroll.
> 2. you read it from top to bottom.
>
>
> But, I am a rails developer where
>
> 1. Backstraces are always HUGE, therefore seldom don't fit in terminal.
> Means LOTS of scrolling to do everytime we get an error.
> 2. in terminal we tend to read backstraces from bottom to top, especially
> when tailing(tail -f) the production logs.
> 3. people, who practice Test-driven development literally spend most of
> their time scrolling to read backstraces to the point most end up buying a
> larger display.
>
> Proposed Solution:
>  Please add a way so we can configure backstraces to be printed in reverse
> order. so if you are reading from bottom, say from terminal, you can get
> the main error message without need to scroll. like this
>
>
>
> stack frame 3
> stack frame 2
> stack frame 1
>  Main Error Message
> .....
>
> this would save lot of time because when the error message is print at the
> bottom, no need to scroll for reading it. Not sure if this can be done
> today. I tried Overriding Exception#backtrace but it caused stack level too
> deep & illegal hardware instruction Error.
>
> Attached are currently what backstrace currently looks like & how there be
> an option to make it look for comparison.
>
>
> --
> http://bugs.ruby-lang.org/
>
>

--089e0160ca3c6c6d0d04e21f11db
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">You can already accomplish something like this yourself:<d=
iv><br></div><div>=C2=A0 =C2=A0 begin</div><div>=C2=A0 =C2=A0 =C2=A0 raise =
&quot;Hello!&quot;</div><div>=C2=A0 =C2=A0 rescue Exception =3D&gt; e</div>=
<div>=C2=A0 =C2=A0 =C2=A0 puts e.backtrace.reverse.join(&quot;\n&quot;)</di=
v>

<div>=C2=A0 =C2=A0 =C2=A0 puts e.message</div><div>=C2=A0 =C2=A0 end</div><=
div><br></div><div>Simple!</div></div><div class=3D"gmail_extra"><br><br><d=
iv class=3D"gmail_quote">On Sat, Jul 20, 2013 at 11:20 PM, gary4gar (Gauris=
h Sharma) <span dir=3D"ltr">&lt;<a href=3D"mailto:gary4gar@gmail.com" targe=
t=3D"_blank">gary4gar@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
Issue #8661 has been reported by gary4gar (Gaurish Sharma).<br>
<br>
----------------------------------------<br>
Feature #8661: Add option to print backstrace in reverse order(stack frames=
 first &amp; error last)<br>
<a href=3D"https://bugs.ruby-lang.org/issues/8661" target=3D"_blank">https:=
//bugs.ruby-lang.org/issues/8661</a><br>
<br>
Author: gary4gar (Gaurish Sharma)<br>
Status: Open<br>
Priority: Normal<br>
Assignee:<br>
Category:<br>
Target version:<br>
<br>
<br>
Currently the way ruby prints the backtrace is that the error comes first &=
amp; then the stack frames. like this<br>
<br>
=C2=A0 Main Error Message<br>
stack frame 1<br>
stack frame 2<br>
stack frame 3<br>
.....<br>
<br>
=C2=A0this is perfectly fine provided<br>
<br>
1. Backstraces are short, so fits in terminal.hence, no need to scroll.<br>
2. you read it from top to bottom.<br>
<br>
<br>
But, I am a rails developer where<br>
<br>
1. Backstraces are always HUGE, therefore seldom don&#39;t fit in terminal.=
 Means LOTS of scrolling to do everytime we get an error.<br>
2. in terminal we tend to read backstraces from bottom to top, especially w=
hen tailing(tail -f) the production logs.<br>
3. people, who practice Test-driven development literally spend most of the=
ir time scrolling to read backstraces to the point most end up buying a lar=
ger display.<br>
<br>
Proposed Solution:<br>
=C2=A0Please add a way so we can configure backstraces to be printed in rev=
erse order. so if you are reading from bottom, say from terminal, you can g=
et the main error message without need to scroll. like this<br>
<br>
<br>
<br>
stack frame 3<br>
stack frame 2<br>
stack frame 1<br>
=C2=A0Main Error Message<br>
.....<br>
<br>
this would save lot of time because when the error message is print at the =
bottom, no need to scroll for reading it. Not sure if this can be done toda=
y. I tried Overriding Exception#backtrace but it caused stack level too dee=
p &amp; illegal hardware instruction Error.<br>


<br>
Attached are currently what backstrace currently looks like &amp; how there=
 be an option to make it look for comparison.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
--<br>
<a href=3D"http://bugs.ruby-lang.org/" target=3D"_blank">http://bugs.ruby-l=
ang.org/</a><br>
<br>
</font></span></blockquote></div><br></div>

--089e0160ca3c6c6d0d04e21f11db--