Can't set catchpoint in .byebugrc

[torbiak]

I want to set a catchpoint for Exception in .byebugrc, but when I add catch Exception to the init file I get the following exception:

Exception `NoMethodError' at /home/jtorbiak/.gem/ruby/2.1.0/gems/byebug-3.5.1/lib/byebug/command.rb:47 - undefined method `frame_pos' for #<Byebug::ControlCommandProcessor::State:0x8ab6258>

I want to set the default catchpoint because in post-mortem mode I can't navigate the stack: where prints out multiple frames, but up/down always say "Can't navigate beyond the newest/oldest frame".

I'm running ruby 2.1.4p265 and byebug 3.5.1.

[deivid-rodriguez]

Hi @torbiak ! Thanks for the report, not only you spotted a bug but two of them. I'll open a separate issue for the other problem you're experiencing.

Hope to have a look into this soon.

[deivid-rodriguez]

@torbiak I've decided to just not allow the catch command in the .byebugrc file. The catch command requires a class name, but during .byebugrc loading I have no associated context (file, line, binding) so I can't check whether the class passed to the command is a valid defined class. I can think of some workarounds to this but we have the set post_mortem setting which does just the same thing, so I decided to just ban this command in .byebugrc.

I'm closing this, but feel free to continue the discussion or reopen this if you don't agree.

[torbiak]

Cool. I totally agree. As I mentioned I only wanted to do this as a temporary workaround for the up/down issue in post-mortem. I should have emphasized that as being the main issue.

Thanks.

[deivid-rodriguez]

👍