cldwalker/debugger

Post Mortem Debugging

tansaku opened this issue · 3 comments

Does debugger support post mortem debugging a la:

http://bashdb.sourceforge.net/ruby-debug.html#Post_002dMortem-Debugging

It's not working for me when I add "Debugger.start(:post_mortem => true)" in the following environment:

RubyGems Environment:

  • RUBYGEMS VERSION: 1.8.25
  • RUBY VERSION: 1.9.3 (2013-02-22 patchlevel 392) [x86_64-darwin12.4.0]
  • INSTALLATION DIRECTORY: /Users/sam/.rvm/gems/ruby-1.9.3-p392
  • RUBY EXECUTABLE: /Users/sam/.rvm/rubies/ruby-1.9.3-p392/bin/ruby
  • EXECUTABLE DIRECTORY: /Users/sam/.rvm/gems/ruby-1.9.3-p392/bin
  • RUBYGEMS PLATFORMS:
    • ruby
    • x86_64-darwin-12
  • GEM PATHS:
    • /Users/sam/.rvm/gems/ruby-1.9.3-p392
    • /Users/sam/.rvm/gems/ruby-1.9.3-p392@global
  • GEM CONFIGURATION:
    • :update_sources => true
    • :verbose => true
    • :benchmark => false
    • :backtrace => false
    • :bulk_threshold => 1000
  • REMOTE SOURCES:

Thanks for reporting your issue! This is one of my 13 active issues. Use that link to check how soon your issue will be answered. Don't forget to check your issue against this project's CONTRIBUTING.md. Cheers.

Hi @tansaku! Post mortem debugging has been broken for a long time in debugger. Have a look at #56.

Post mortem support should work just fine in byebug but you would need to upgrade your ruby.... (you probably should anyways!).

Salud.

This is a duplicate of #56. Pull requests welcome