question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Using Chromium and Chrome Debugger On Linux

See original GitHub issue

UPDATE! I got your extension to open Chromium OK and connect to the debugger 😃:

Maybe you could comment if I did this the best way, and also if there is a way for the Chromium tab to close when the live-server connection is closed? THANKS.

"liveServer.settings.AdvanceCustomBrowserCmdLine": "/usr/bin/chromium-browser --remote-debugging-port=9222"
{
    "version": "0.1.0",
    "configurations": [
        {
            "name": "Attach",
            "type": "chrome",
            "request": "attach",
            "port": 9222,
            "url": "http://127.0.0.1:5500/",
            "webRoot": "${workspaceRoot}"
        }
    ]
}

Hello,

I am trying to use live-server and chrome debugger on Linux with Chromium. If I want to use Chromium rather than Chrome in the debugger my settings used to look something like:

{
    "version": "0.2.0",
    "configurations": [{
        "type": "chrome",
        "runtimeExecutable": "/usr/bin/chromium-browser",
        "runtimeArgs": [
            "--remote-debugging-port=9222"
        ],
        "request": "launch",
        "name": "Chromium against localhost",
        "url": "http://localhost:8080",
        "webRoot": "${workspaceRoot}",
        "sourceMaps": false,
        "smartStep": false
    }]
}

but in live server when I try to make it open changing the preferences to:

"liveServer.settings.ChromeDebuggingAttachment": true,
"liveServer.settings.CustomBrowser": "chrome",

then nothing happens as live-server can’t know to open Chromium.

Can you add an option for Chromium, or is there something I can do? If I type ‘chromium’ on my command line it does not run at the moment as it’s not in the PATH. I can fix that if needed, but being able to point to the executable in your extension could be cool too.

Cheers!

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
David-Elsecommented, Jan 29, 2019

@DzenetanMassart Yes, I have been using it for ages on Fedora. In VS Code settings I have:

"liveServer.settings.ChromeDebuggingAttachment": true,
"liveServer.settings.AdvanceCustomBrowserCmdLine": "/usr/bin/chromium-browser --remote-debugging-port=9222",
0reactions
DzenetanMassartcommented, Jan 29, 2019

So… and now, can we use Live Server with Chromium?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Tips for debugging on Linux
This page is for Chromium-specific debugging tips; learning how to run gdb ... On distributions that use the Yama LSM (that includes Ubuntu...
Read more >
Chromium on Chromium OS Debugging Tips
We recommend that developers use gdb to debug their Chromium-based OS. The gdb is already included in the chromium os image. You can...
Read more >
debug chromium in linux - Google Groups
My question is if it's practical to use eclipse in Chromium case? ... I don't always debug on Linux, but when I do...
Read more >
Chromium/Debugging - Ubuntu Wiki
If Chromium crashes and you want to file a bug upstream, use their linux template. Always include the output from the following command:....
Read more >
debug Chromium with gdb under Ubuntu - Brook Hong
Debugging existing Tab · Shift-Esc to open Task manager of Chromium, get the process id of the Tab you'd like to debug ·...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found