blocks|key|1451968|text|Exception#backtrace包含整个堆栈：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1451969|def+do_division_by_zero;+5+/+0;+end
begin
++do_division_by_zero
rescue+=>+exception
++puts+exception.backtrace
++raise+#+always+reraise
end|code-block|syntax|javascript|1451970|(灵感来自彼得·库珀的Ruby+Inside博客)|offset|length|1451971|entityMap|0|LINK|mutability|MUTABLE|url|http://www.rubyinside.com/21-ruby-tricks-902.html^0|0|0|B|B|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

Exception#backtrace has the entire stack in it:

<pre><code>def do_division_by_zero; 5 / 0; end
begin
 do_division_by_zero
rescue =&gt; exception
 puts exception.backtrace
 raise # always reraise
end
</code></pre>

(Inspired by Peter Cooper's <a href="http://www.rubyinside.com/21-ruby-tricks-902.html" rel="noreferrer">Ruby Inside</a> blog)

blocks|key|1452004|text|IRB为这个可怕的“功能”提供了一个设置，您可以对其进行自定义。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1452005|创建一个名为~/.irbrc的文件，其中包含以下行：|offset|length|style|CODE|1452006|IRB.conf[:BACK_TRACE_LIMIT]+=+100|code-block|syntax|javascript|1452007|这将允许您至少在irb中看到100个堆栈帧。我还没有找到非交互式运行时的等效设置。|1452008|有关IRB自定义的详细信息可以在Pickaxe+book中找到。|1452009|entityMap|0|LINK|mutability|MUTABLE|url|http://www.rubycentral.com/book/irb.html^0|0|6|8|0|0|8|3|0|G|C|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|12|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|O|3|P|5|6|7|16|8|@]|9|@$D|17|E|18|1|19]]|A|$]]|$1|Q|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

IRB has a setting for this awful "feature", which you can customize.

Create a file called <code>~/.irbrc</code> that includes the following line:

<pre><code>IRB.conf[:BACK_TRACE_LIMIT] = 100
</code></pre>

This will allow you to see 100 stack frames in <code>irb</code>, at least. I haven't been able to find an equivalent setting for the non-interactive runtime.

Detailed information about IRB customization can be found in the <a href="http://www.rubycentral.com/book/irb.html" rel="noreferrer">Pickaxe book</a>.

blocks|key|1667064|text|当我试图加载我的测试环境(通过rake+test或autotest)时，我得到了这些错误，IRB的建议没有帮助。我最终将整个test/test_helper.rb封装在一个begin/rescue块中，这样就解决了问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1667065|begin
++class+ActiveSupport::TestCase
++++#awesome+stuff
++end
rescue+=>+e
++puts+e.backtrace
end|code-block|syntax|javascript|1667066|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I was getting these errors when trying to load my test environment (via rake test or autotest) and the IRB suggestions didn't help. I ended up wrapping my entire test/test_helper.rb in a begin/rescue block and that fixed things up.

<pre><code>begin
 class ActiveSupport::TestCase
 #awesome stuff
 end
rescue =&gt; e
 puts e.backtrace
end
</code></pre>

blocks|key|1667096|text|这将生成错误描述和简洁、缩进的堆栈跟踪：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1667097|begin+++++++++++++++
+#+Some+exception+throwing+code
rescue+=>+e
++puts+"Error+during+processing:+#{$!}"
++puts+"Backtrace:\n\t#{e.backtrace.join("\n\t")}"
end|code-block|syntax|javascript|1667098|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This produces the error description and nice clean, indented stacktrace:

<pre><code>begin 
 # Some exception throwing code
rescue =&gt; e
 puts "Error during processing: #{$!}"
 puts "Backtrace:\n\t#{e.backtrace.join("\n\t")}"
end
</code></pre>

blocks|key|1667144|text|如果你想要一个简单的一行代码，你也可以这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1667145|puts+caller|code-block|syntax|javascript|1667146|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You could also do this if you'd like a simple one-liner:

<pre><code>puts caller
</code></pre>

blocks|key|1667198|text|这模仿了官方的Ruby跟踪，如果这对你很重要的话。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1667199|begin
++0/0++#+or+some+other+nonsense
rescue+=>+e
++puts+e.backtrace.join("\n\t")
+++++++.sub("\n\t",+":+#{e}#{e.class+?+"+(#{e.class})"+:+''}\n\t")
end|code-block|syntax|javascript|1667200|有趣的是，它没有正确地处理“未处理的异常”，报告为“RuntimeError”，但位置是正确的。|1667201|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

This mimics the official Ruby trace, if that's important to you.

<pre><code>begin
 0/0 # or some other nonsense
rescue =&gt; e
 puts e.backtrace.join("\n\t")
 .sub("\n\t", ": #{e}#{e.class ? " (#{e.class})" : ''}\n\t")
end
</code></pre>

Amusingly, it doesn't handle 'unhandled exception' properly, reporting it as 'RuntimeError', but the location is correct.

blocks|key|1667229|text|用于callstack的一个内联：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1667230|begin;+Whatever.you.want;+rescue+=>+e;+puts+e.message;+puts;+puts+e.backtrace;+end|code-block|syntax|javascript|1667231|一个不带所有gem的callstack的内联：|1667232|begin;+Whatever.you.want;+rescue+=>+e;+puts+e.message;+puts;+puts+e.backtrace.grep_v(/\/gems\//);+end|1667233|没有所有gem的调用堆栈的一个内联程序，并且是相对于当前目录的|1667234|begin;+Whatever.you.want;+rescue+=>+e;+puts+e.message;+puts;+puts+e.backtrace.grep_v(/\/gems\//).map+{+%7Cl%7C+l.gsub(`pwd`.strip+%2B+'/',+'')+};+end|1667235|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

One liner for callstack:

<pre><code>begin; Whatever.you.want; rescue =&gt; e; puts e.message; puts; puts e.backtrace; end
</code></pre>

One liner for callstack without all the gems's:

<pre><code>begin; Whatever.you.want; rescue =&gt; e; puts e.message; puts; puts e.backtrace.grep_v(/\/gems\//); end
</code></pre>

One liner for callstack without all the gems's and relative to current directory

<pre><code>begin; Whatever.you.want; rescue =&gt; e; puts e.message; puts; puts e.backtrace.grep_v(/\/gems\//).map { |l| l.gsub(`pwd`.strip + '/', '') }; end
</code></pre>

blocks|key|1452263|text|您也可以使用backtrace+Ruby+gem+(我是作者)：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1452264|require+'backtrace'
begin
++#+do+something+dangerous
rescue+StandardError+=>+e
++puts+Backtrace.new(e)
end|code-block|syntax|javascript|1452265|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/yegor256/backtrace^0|6|9|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

You can also use <a href="https://github.com/yegor256/backtrace" rel="nofollow noreferrer">backtrace</a> Ruby gem (I'm the author):

<pre><code>require 'backtrace'
begin
 # do something dangerous
rescue StandardError =&gt; e
 puts Backtrace.new(e)
end
</code></pre>

blocks|key|1452311|text|几乎每个人都回答了这个问题。我将任何rails异常打印到日志中的版本是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1452312|begin
++++some_statement
rescue+=>+e
++++puts+"Exception+Occurred+#{e}.+Message:+#{e.message}.+Backtrace:++\n+#{e.backtrace.join("\n")}"
++++Rails.logger.error+"Exception+Occurred+#{e}.+Message:+#{e.message}.+Backtrace:++\n+#{e.backtrace.join("\n")}"
end|code-block|syntax|javascript|1452313|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Almost everybody answered this. My version of printing any rails exception into logs would be:
<pre><code>begin
 some_statement
rescue =&gt; e
 puts &quot;Exception Occurred #{e}. Message: #{e.message}. Backtrace: \n #{e.backtrace.join(&quot;\n&quot;)}&quot;
 Rails.logger.error &quot;Exception Occurred #{e}. Message: #{e.message}. Backtrace: \n #{e.backtrace.join(&quot;\n&quot;)}&quot;
end
</code></pre>

When I get exceptions, it is often from deep within the call stack. When this happens, more often than not, the actual offending line of code is hidden from me:

<pre class="lang-none prettyprint-override"><code>tmp.rb:7:in `t': undefined method `bar' for nil:NilClass (NoMethodError)
 from tmp.rb:10:in `s'
 from tmp.rb:13:in `r'
 from tmp.rb:16:in `q'
 from tmp.rb:19:in `p'
 from tmp.rb:22:in `o'
 from tmp.rb:25:in `n'
 from tmp.rb:28:in `m'
 from tmp.rb:31:in `l'
 ... 8 levels...
 from tmp.rb:58:in `c'
 from tmp.rb:61:in `b'
 from tmp.rb:64:in `a'
 from tmp.rb:67
</code></pre>

That "... 8 levels..." truncation is causing me a great deal of trouble. I'm not having much success googling for this one: How do I tell ruby that I want dumps to include the full stack?

How do I get ruby to print a full backtrace instead of a truncated one?

当我得到异常时，它通常来自调用堆栈的深层。当这种情况发生时，实际的违规代码行通常会对我隐藏起来：tmp.rb:7:in `t': undefined method `bar' for nil:NilClass (NoMethodError)        from tmp.rb:10:in `s'        fro...

问如何让ruby打印完整的回溯而不是截断的回溯？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何让ruby打印完整的回溯而不是截断的回溯？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何让ruby打印完整的回溯而不是截断的回溯？
EN