Debugger failed to parse: [xmldom error]

tgmerritt commented 4 years ago

There are times when I click within VS Code to set a debug point, and I immediately get:

Debugger failed to parse: [xmldom error]    element parse error: Error: attribute value must after "="
@#[line:1,col:1]
For: <eval expression="ro

In the debug console.

Other times I click the set the breakpoint and there is no error. Whenever I get this xmldom error, the debugger does not break on the breakpoint.

ruby-debug-ide (0.7.2, 0.7.0)
    Author: Markus Barchfeld, Martin Krauskopf, Mark Moseley, JetBrains
    RubyMine Team
    Homepage: https://github.com/ruby-debug/ruby-debug-ide
    License: MIT
    Installed at (0.7.2): /Users/tyler/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0
                 (0.7.0): /Users/tyler/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0

    IDE interface for ruby-debug.

debase (0.2.4.1)
    Author: Dennis Ushakov
    Homepage: https://github.com/denofevil/debase
    License: MIT
    Installed at: /Users/tyler/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0

    debase is a fast implementation of the standard Ruby debugger
    debug.rb for Ruby 2.0

rkiller commented 4 years ago

getting same error

sauloarruda commented 4 years ago

+1

rnasc commented 3 years ago

I'm having this issue as well.

sec0ndhand commented 3 years ago

+1

yock commented 3 years ago

Does Rubymine also use this package to drive the Ruby debugger? I seem to only get this error in VSCode and not Rubymine and I wonder if there is something significantly different in their integrations.

hurricup commented 3 years ago

@yock it does in some cases. Always for ruby 3.0 and for other versions if use experimental debugger checkbox is checked.

shenrie commented 3 years ago

FWIW, I also get this error using Ruby 2.4.7 when hitting a breakpoint and trying to dump values into the debug console from the command line. For example, I can dump User.all just fine, but then if I try to view any one user like User.find(3)then I get the same reported error.

shenrie commented 3 years ago

Two successful and one failure

xjose97x commented 2 years ago

I can confirm the problem still persists.

davidhin commented 2 years ago

Issue still exists on my end, ruby 2.6.3

ritajie commented 1 year ago

+1, any solutions now? 🤯

ruby-debug / ruby-debug-ide

Debugger failed to parse: [xmldom error] #196