API for stopping the debugger
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 30/100
Rechercherichtung
No file or test is named. Begin by locating the debugger's public API and the DEBUGGER__::SESSION@server behavior described here; completion would require a documented way to stop the loaded debugger during execution and validation that RubyMine can attach without the reported hang.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Apologies if such a feature is already present, I couldn't find it in the project.
Could I request an API method to stop the debugger once it's been loaded? I'm from the RubyMine team, and our use case for this is the following: the users would like to be able to launch their program and then later attach our debugger to it. Our debugger conflicts with the debug gem, however, so if the user project contains this gem (and Rails apps include it by default), then the attaching our debugger will lead to problems (mostly hanging, I think). The debug gem is loaded at the program start, so if we try to attach our debugger later, we cannot disable the debugger from debug, and so our debugger won't work; the only way to disable it is by setting the environment variable RUBY_DEBUG_ENABLE before launching the program, but that is up to the user only, not to RubyMine (if they launch their app in the terminal, not via an RM run configuration). So, is it or would it be possible to shut the debugger down completely during execution? Then we could call such a hypothetical stop method upon starting our debugger, and everything would work.
To be more precise, one of the incompatibilities is that our debugger hangs at the DEBUGGER__::SESSION@server thread, though there may be other issues as well.
- Vorherrschende Sprache
- Ruby
- Sterne
- 1.3k
- Forks
- 146
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus ruby/debug
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 68/100
-
Support exceptionOptions in setExceptionBreakpoints to catch arbitrary exception classes via DAP Offen
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 55/100
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 45/100
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 52/100
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
Ähnliche Issues
-
SyncEm always forwards a dummy block, so wrapped methods lose their no-block/Enumerator behavior Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
endoflife-date/endoflife.date#11086 ·
-
internal
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
Kong/developer.konghq.com#7322 ·
-
bug P2
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100