nixme/pry-debugger issues and pull requests

#63 - `require': cannot load such file -- pry-debugger (LoadError)

Issue - State: open - Opened by sginsbourg about 6 years ago - 1 comment

#62 - License issue

Issue - State: open - Opened by charignon about 7 years ago - 2 comments

#61 - Overwrites any local variables named "step"

Issue - State: open - Opened by AndrewRayCode over 7 years ago

#60 - next keyword hijacked in loop

Issue - State: open - Opened by br3nt almost 10 years ago - 3 comments

#59 - Unable to install with ruby version 2.1.4

Issue - State: closed - Opened by jonyt almost 10 years ago - 1 comment

#58 - Pry-remote show address already in use when quit from rails app

Issue - State: open - Opened by kdstarter about 10 years ago - 11 comments

#57 - Next command is leaving current stack frame

Issue - State: open - Opened by jmondo over 10 years ago - 3 comments

#56 - I cannot type an 'o', 'p', or 'v' inside the pry-debugger.

Issue - State: open - Opened by vrsean over 10 years ago

#55 - Confusing behavior of `n`, terminating a Rails console

Issue - State: closed - Opened by dblock over 10 years ago - 30 comments

#54 - Release a patch version that works with Pry v0.10

Issue - State: closed - Opened by teohm over 10 years ago - 3 comments

#53 - debugger recommend using byebug for ruby 2.x

Pull Request - State: closed - Opened by hackjoy over 10 years ago - 3 comments

#52 - Fails to install on Ruby 2.1.2p95: Failed to build gem native extension

Issue - State: closed - Opened by Lordnibbler over 10 years ago - 3 comments

#51 - Crashes when using multithreading

Issue - State: open - Opened by dhawal55 over 10 years ago

#50 - next does not work (windows)

Issue - State: closed - Opened by dhawal55 over 10 years ago - 4 comments

#49 - Finish does not return to where `step` was called

Issue - State: open - Opened by jackdesert over 10 years ago

#48 - break --show doesn't work

Issue - State: open - Opened by agrberg over 10 years ago

#47 - next working as step

Issue - State: closed - Opened by AHaymond over 10 years ago - 2 comments

#46 - Segmentation fault

Issue - State: open - Opened by artofhuman almost 11 years ago - 2 comments

#45 - Pry-debugger won't install on MRI 2.1.0-preview2

Issue - State: open - Opened by andyl almost 11 years ago - 6 comments

#44 - `break --condition` doesn't parse right

Issue - State: open - Opened by Sharpie about 11 years ago - 2 comments

#43 - Add a Bitdeli Badge to README

Pull Request - State: closed - Opened by bitdeli-chef about 11 years ago

#42 - How can you tell where in the code you are, when stepping through?

Issue - State: open - Opened by JJJollyjim about 11 years ago - 2 comments

#41 - Requested Feature: Be able to step into an arbitrary snippet of code

Pull Request - State: closed - Opened by jackdesert about 11 years ago - 1 comment

#40 - next and step seems to works as same

Issue - State: closed - Opened by GCorbel over 11 years ago - 7 comments

#39 - debugger not work

Issue - State: closed - Opened by artofhuman over 11 years ago - 4 comments

#38 - enable setting of breakpoints at a given line of a method

Issue - State: open - Opened by banister over 11 years ago
Labels: enhancement

#37 - Use debugger aliases only when pry-debugger is available.

Pull Request - State: closed - Opened by arnab over 11 years ago - 4 comments

#36 - malloc: possible integer overflow (ArgumentError)

Issue - State: closed - Opened by kyrylo over 11 years ago - 1 comment

#35 - Rubinius::Debugger support

Issue - State: closed - Opened by tamird over 11 years ago - 2 comments

#34 - next erroneously behaves like step [MRI 2.0]

Issue - State: open - Opened by FND over 11 years ago - 9 comments

#33 - Allow pry versions greater than 0.9.x

Pull Request - State: closed - Opened by rking over 11 years ago - 4 comments

#32 - 'next' navigates into pry-debugger/processor.rb code

Issue - State: closed - Opened by twelve17 over 11 years ago - 8 comments

#31 - Add standard aliases for continue, step, next, finish commands

Pull Request - State: closed - Opened by iogakos over 11 years ago - 14 comments

#30 - Feature Request: Need a Way to Try Next Line

Issue - State: closed - Opened by jackdesert over 11 years ago - 3 comments

#29 - Failed compiling for Ruby2.0.0p0 x64 under windows

Issue - State: closed - Opened by Crossverse over 11 years ago - 4 comments

#28 - Upgrade the dependency for debugger

Pull Request - State: closed - Opened by JosephKu over 11 years ago - 1 comment

#27 - backtrace come out in large quantities in and pry + rcodetools have pry-debugger

Issue - State: open - Opened by akicho8 over 11 years ago

#26 - jruby 1.7.2 cannot install pry-debugger gem

Issue - State: closed - Opened by bzbdev001 over 11 years ago - 1 comment

#25 - debugger-linecache fails to build under Rubinius 2.0 (dcd08)

Issue - State: closed - Opened by kfatehi over 11 years ago - 1 comment

#24 - pry won't start on 1.9.3-p392

Issue - State: closed - Opened by ivanoats over 11 years ago - 2 comments

#23 - Ruby 2.0 dependencies

Issue - State: closed - Opened by avit over 11 years ago - 4 comments

#22 - Keep running pry-remote instead of starting pry-remote session everytime

Issue - State: open - Opened by sathish316 almost 12 years ago - 5 comments

#21 - allow breaking on REPL-defined mehods

Pull Request - State: closed - Opened by banister about 12 years ago

#20 - Safer monkey-patching of Pry.start/.teardown

Pull Request - State: closed - Opened by benizi about 12 years ago - 2 comments

#19 - Update debugger version

Pull Request - State: closed - Opened by jshou about 12 years ago - 2 comments

#18 - Fixed breakpoint location parsing issue

Pull Request - State: closed - Opened by nviennot about 12 years ago - 1 comment

#17 - Dependency on old debugger. Won't work with 1.2.0

Issue - State: closed - Opened by noctivityinc about 12 years ago - 3 comments

#16 - nested breakpoints dont work

Issue - State: open - Opened by banister over 12 years ago

#15 - 'exit' when debugging in REPL puts pry into a broken state

Issue - State: open - Opened by banister over 12 years ago

#14 - 'break' command doesn't work on methods defined inside pry

Issue - State: closed - Opened by banister over 12 years ago - 3 comments

#13 - Finish should know which frame you're currently on

Pull Request - State: open - Opened by jasonLaster over 12 years ago

#12 - Add support for pry-stack_explorer in pry_debugger

Pull Request - State: open - Opened by jasonLaster over 12 years ago - 7 comments

#11 - Clear screen after "next", "continue", etc.

Issue - State: open - Opened by jmuheim over 12 years ago - 1 comment

#10 - loosen pry dependency so it'll work with Pry release 0.9.10

Pull Request - State: closed - Opened by banister over 12 years ago - 1 comment

#9 - `continue` command exits Pry session

Issue - State: closed - Opened by hahuang65 over 12 years ago - 5 comments

#8 - pry-stack_explorer doesn't work from breakpoints

Issue - State: open - Opened by nixme over 12 years ago - 3 comments
Labels: bug

#7 - Work with debugger-pry

Issue - State: open - Opened by nixme over 12 years ago
Labels: bug

#6 - Thread safety

Issue - State: open - Opened by nixme over 12 years ago
Labels: bug

#5 - Reuse pry instance

Issue - State: closed - Opened by nixme over 12 years ago
Labels: enhancement

#4 - Skip to a line number

Issue - State: open - Opened by nixme over 12 years ago
Labels: enhancement

#3 - Exception/Catchpoints

Issue - State: open - Opened by nixme over 12 years ago
Labels: enhancement

#2 - Watchpoints

Issue - State: open - Opened by nixme over 12 years ago
Labels: enhancement

#1 - Breakpoints

Issue - State: closed - Opened by nixme over 12 years ago
Labels: enhancement

GitHub / nixme/pry-debugger issues and pull requests