# RSpec swallowing huge chunks of my backtraces **URL:** \ **Category:** Ruby\ **Created:** [October 27, 2009, 12:37am UTC](https://www.ruby-forum.com/t/rspec-swallowing-huge-chunks-of-my-backtraces/177940 "2009-10-27T00:37:49Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![murfhy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/d26b3c/32.png) [@murfhy](https://www.ruby-forum.com/u/murfhy)\ **Post date:** [October 27, 2009, 12:37am UTC](https://www.ruby-forum.com/t/rspec-swallowing-huge-chunks-of-my-backtraces/177940/1 "2009-10-27T00:37:49Z")
I don’t know exactly when this started happening, but it seems like RSpec recently started swallowing huge chunks of the backtrace. Sometimes I don’t even get one. This is making it extremely annoying to debug as I’m unable to see where the error is occurring. Anyone know what’s up? ---
**Author:** ![murfhy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/d26b3c/32.png) [@murfhy](https://www.ruby-forum.com/u/murfhy)\ **Post date:** [October 29, 2009, 4:02pm UTC](https://www.ruby-forum.com/t/rspec-swallowing-huge-chunks-of-my-backtraces/177940/2 "2009-10-29T16:02:54Z")
On Mon, Oct 26, 2009 at 7:37 PM, Tony A. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > I don’t know exactly when this started happening, but it seems like RSpec > recently started swallowing huge chunks of the backtrace. Â Sometimes I don’t > even get one. > > This is making it extremely annoying to debug as I’m unable to see where the > error is occurring. > > Anyone know what’s up? I started noticing the same thing today: 1. NoMethodError in ‘XML::Importer should extract a list of jobs from the provided XML’ You have a nil object when you didn’t expect it! The error occurred while evaluating nil.text Finished in 0.03372 seconds 1 example, 1 failure It would be awesome to know what line that was occurring on… Best, Michael G. ---
**Author:** ![murfhy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/d26b3c/32.png) [@murfhy](https://www.ruby-forum.com/u/murfhy)\ **Post date:** [October 30, 2009, 3:06pm UTC](https://www.ruby-forum.com/t/rspec-swallowing-huge-chunks-of-my-backtraces/177940/3 "2009-10-30T15:06:11Z")
On Thursday 29 October 2009, Michael G. wrote: > |I started noticing the same thing today: > | > |It would be awesome to know what line that was occurring on… > | > |Best, > |Michael G. > | I noticed something like that recently (at least using ruby 1.9) and solved it by passing the -b option to spec. I don’t know the reason for this change. I tried looking at the rspec CHANGELOG but it didn’t show anything related (at least, I didn’t recognize it). I hope this helps Stefano ---
**Author:** ![murfhy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/d26b3c/32.png) [@murfhy](https://www.ruby-forum.com/u/murfhy)\ **Post date:** [November 2, 2009, 3:47am UTC](https://www.ruby-forum.com/t/rspec-swallowing-huge-chunks-of-my-backtraces/177940/4 "2009-11-02T03:47:16Z")
On Fri, Oct 30, 2009 at 9:05 AM, Stefano C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > | > > |1 example, 1 failure > > least, I didn’t recognize it). > > I hope this helps Thanks, this helps, now when I need a detailed backtrace I can just add -b to spec/spec.opts Michael G.