Ruby 2.5.3 and bootsnap still not working #66
Comments
|
@brodock Do you debug with RubyMine? |
|
@ViugiNick yes |
(will fix at least ruby-debug#69 ruby-debug#66 ruby-debug#64 ruby-debug/ruby-debug-ide#146 )
(will fix at least #69 #66 #64 ruby-debug/ruby-debug-ide#146 )
|
@brodock Can you try the last version of |
|
I commented in RubyMine YouTrack as well, but perhaps this is the right GitHub issue to continue discussion... (Landed here from Shopify/bootsnap#168) I'm experiencing not-working breakpoints in RubyMine with:
The workaround of commenting out bootsnap makes the breakpoints behave correctly. Is there a specific version of something that I should try upgrading to and see if this is fixed? Also, is this the right issue on GitHub to track the state of this problem? Happy to try to provide other info if it would help! |
|
@mkasberg Could you please try RubyMine 2019.3 Beta? |
|
Thanks for the reply! I tested the behavior I'm observing with the following versions:
I did not observe any behavior difference between these versions and RubyMine 2019.2. That is to say, Bootsnap still appears to prevent my breakpopints from working in the most recent version of RubyMine 2019.3 Beta. While testing this, however, I did observe some interesting behavior in both versions - if I:
Breakpoints continue to work even with bootsnap uncommented. (I haven't confirmed how long this will last...) (Perhaps something to do with how/when the cache was built?) I'm happy to try other things if there's anything that might help resolve this! Right now, I comment out bootsnap whenever I need my breakpoints to work, and it would be nice not to have to do so. |
|
@mkasberg Ok, is it possible to share some example, so I can reproduce the problem, maybe you place breakpoints in some specific locations? |
|
I don't have an example I can share that's immediately available, but I will work on a minimal example to reproduce the problem. (Maybe I'll even figure something out in the process.) I'll get back to you in a few days if I can get something that's small and reproducible. |
|
The process of constructing a minimal example actually helped me track down the source of the problem. As it turns out, the solution was very simple. Upgrading to Bootsnap 1.4.5 solved the problem for me due to Shopify/bootsnap#257. I was under the impression I didn't need to do this on Ruby 2.5.5 due to this comment, but as it turns out the upgrade to Bootsnap 1.4.5 was still necessary, even on Ruby 2.5.5. With the Bootsnap upgrade, no other changes were necessary and my breakpoints are working. Anyway, thanks for being my rubber duck! Hopefully my comment will help someone else who comes across this... |
|
Also, I do now have a fairly minimal example I could share if that would be useful for any of your testing purposes... |
|
@mkasberg Could you e-mail it to me, please? or attach it here |
|
Sure! mkasberg-breakpoints.zip Steps to reproduce are in the README in the zipped folder. |
|
@mkasberg Are you ok with upgrading bootsnap gem? |
|
Yep, already did it! Thanks for the help! |
|
Closing as abandoned. Feel free to provide most recent information after checking most recent debase version. |
I've followed this issue: Shopify/bootsnap#168 but it looks like it's not the iseq that is breaking. Here is the output I get:
The text was updated successfully, but these errors were encountered: