Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debugger failed to parse: [xmldom error] #196

Open
tgmerritt opened this issue Jul 6, 2020 · 11 comments
Open

Debugger failed to parse: [xmldom error] #196

tgmerritt opened this issue Jul 6, 2020 · 11 comments

Comments

@tgmerritt
Copy link

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
Copy link

rkiller commented Sep 30, 2020

getting same error

@sauloarruda
Copy link

+1

@rnasc
Copy link

rnasc commented Oct 18, 2020

I'm having this issue as well.

@sec0ndhand
Copy link

+1

@yock
Copy link

yock commented Mar 19, 2021

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
Copy link
Contributor

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

@shenrie
Copy link

shenrie commented May 15, 2021

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
Copy link

shenrie commented May 15, 2021

image

Two successful and one failure

@xjose97x
Copy link

I can confirm the problem still persists.

@davidhin
Copy link

Issue still exists on my end, ruby 2.6.3

@ritajie
Copy link

ritajie commented Nov 7, 2022

+1, any solutions now? 🤯

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests