Can we make it as a vs code plug-in?

Hi dear developer. I have follewed your project about 2 years from gdb-imagewatch. It is an awesome work! I love it!
Recently I have been looking for a image-watch like plug-in on VS Code, but turn out nothing. I wonder if we can use your project to make a plug-in to do OpenCV mat memory view inside VS Code.
Do you have a plan to do it or can you accept someone else to do this work?

@YihaoWEI

Hi, @YihaoWEI thanks for getting in touch and using our project, we are really happy to hear that :D

Yes, I think it is possible to package it as a plugin for a few IDEs (VSCode, CLion/AndroidStudio, Atom and whatnot). We have the intention to do so indeed, but we do not have concrete plans yet as we currently do not have enough free time to do so. We also want to explore other types of packaging such as Debian packages.

So, answering your last question directly: contributions are definitely welcome :D It would be really nice to set up an architecture that enables different packaging targets.

Also, I believe OID should work out-of-the-box with VSCode if you add the "source" command to your .gdbinit or .lldbinit file. I will test it as soon as I can and then I will keep you updated.

Thanks brunoalr! I have already made it realized using .gdbinit inside VSCode. It works very well as usual.
I'm studying inside VSCode to see if it is possible to make it as a plug-in tool.
Hope I can finish it soon :D

Stale issue message

@YihaoWEI

@YihaoWEI
python /path/oid.py --test works well.
Then i tried source /path/oid.py, but got an error:

Any ideas?

@wuwuzhijing

@wuwuzhijing please follow the instructions from the readme: https://github.com/OpenImageDebugger/OpenImageDebugger#building-the-open-image-debugger

For gdb, you have to call source /path/oid.py when running gdb or add this line to ~/.gdbinit

@brunoalr

@brunoalr
Also added source /path/oid.py to ~/.gdbinit, but no GUI appeared when running gdb(I am sure that Mat in buffer exists).
P.S. I followed the readme very strict. After getting rid of a lot of envirment error, still not working.

@brunoalr

@brunoalr
Can you figure out the problem?

@wuwuzhijing

@wuwuzhijing I can help :)
I need more information first:

OID's commit hash
operating system and version
gdb version
lldb version
python2 and python3 versions
more detailed reproduction steps and error messages, if possible

(I actually plan to create an issue template to ask for this kind of information :) )

@brunoalr

@brunoalr
Thank you for your attention.

basic config

OID commit hash
1ba720cf9ad6ab8e3e0f3455ed41bd337b4e6f74
OS
Ubuntu 20.04.1
gdb version
9.2
python3 version
3.8.8
python2 version
2.7.18

reproduction steps

build

git clone https://github.com/OpenImageDebugger/OpenImageDebugger.git
cd OpenImageDebugger
git submodule init
git submodule update
mkdir build && cd build
cmake ..
make -j4
make install

settings
source /mypath/OpenImageDebugger/oid.py
open VSCode and open CMake project
Set gdb debug file(that is launch.json) as follows:
Set Breakpoint
Press F5, debug start
Press F10, debug step by step. Here, no gui appeared.

If you need more info. , I will add later.

vscode+wsl2, debug from console, What should I do?

I like image watch very much under windows, but It was very frustrating for me under linux

@brunoalr

@brunoalr @mwwzbinf, It's not a plugin for vscode but I'm working on an integration using devcontainer-features which integrates with devcontainers quite easily. I start the project here: dakhouya/devcontainer-features

It is still a work in progress and I mainly use it to debug c++ code with gbd so maybe there's thing missing for lldb.

References for the devcontainers
https://code.visualstudio.com/docs/devcontainers/containers
https://containers.dev/overview

Interesting idea! I will take a look at it when I have time.

@brunoalr

Hi @brunoalr,

I am trying to use OID with CodeLLDB and vscode. But I cannot open the OID window now.

This is my lauch.json:

{
    "type": "lldb",
    "request": "launch",
    "name": "Launch",
    "program": "${workspaceFolder}/build/TestOpenImageDebugger",
    "args": [],
    "cwd": "${workspaceFolder}",
    // "initCommands": ["command source ${env:HOME}/.lldbinit"],
},

Could you please give me some help with this? Thank you for the help.

My env is

OID version (commit or tag): v1.19.0 or v1.23.49
OS and Version: M1 MacOS
Which debugger [gdb and/or lldb] and respective versions: lldb version 19.1.7
Python version: Python 3.13.2

Before I moved to vscode and CodeLLDB, I have installed OID successfully and I can run python3 /path/install/oid.py --test and lldb test and pop out GUI successfully. (also writed into ~/.lldbinit).

This is the screenshot when I manually used lldb:

@JiahangWu

Hi @JiahangWu, thanks for the detailed report :) So far, I haven't tried to use the codelldb plugin as I usually rely on the CLI of the debuggers myself - thus we are not supporting it as of of now - that reminds me I should make it clearer on the README which configurations are supported 😅, but after all, this is mostly a hobby project for me. I will try to take a look at the plugin using the config you provided, but I cannot promise when I will do it neither if I will succeed.

@JiahangWu

@JiahangWu try this (using your own paths and names...):

OpenImageDebugger/tesbench/.vscode/launch.json

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "lldb",
            "request": "launch",
            "name": "Debug",
            "program": "${workspaceFolder}/build/testbench",
            "args": [],
            "cwd": "${workspaceFolder}",
            "initCommands": ["command script import <path to OID installation>/oid.py"],
        }
    ]
}

OpenImageDebugger/tesbench/.vscode/settings.json

{    
    "lldb.library": "/opt/homebrew/Cellar/llvm/19.1.7_1/lib/liblldb.19.1.7.dylib"
}

Then start debugging with F5, not the "Debug" button in the status bar. I am not sure which of the gazillion plugins is responsible for the status bar button, probably CMake-tools.

Ohhhh! It works now. Thank you so much!

no problem, glad to help :)

@brunoalr

Hi @brunoalr,
I briefly wrote an instruction to use OID on MacOS(https://github.com/JiahangWu/OpenImageDebugger). Please feel free to integrate it into your README.md if it's useful.

Hi everyone, sorry for the very long delay on this one 😅

Good news though: there is now an official Open Image Debugger extension for VS Code (and forks like Cursor, VSCodium, Windsurf, etc.), so the original question from this issue is finally answered — yes, you can use it as a VS Code plugin :D

You can grab it from:

VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=OpenImageDebugger.openimagedebugger-vscode
Open VSX: https://open-vsx.org/extension/openimagedebugger/openimagedebugger-vscode

I also just released a plugin for CLion and Android Studio: https://plugins.jetbrains.com/plugin/33640-open-image-debugger :D

Navigation Menu

Repository navigation

Can we make it as a vs code plug-in? #15

basic config

reproduction steps

If you need more info. , I will add later.

5 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Can we make it as a vs code plug-in? #15

Description

Activity

brunoalr commented on Aug 13, 2020

YihaoWEI commented on Aug 25, 2020

github-actions commented on Jun 27, 2021

wuwuzhijing commented on Sep 15, 2021

brunoalr commented on Sep 15, 2021

wuwuzhijing commented on Sep 15, 2021

wuwuzhijing commented on Sep 17, 2021

brunoalr commented on Sep 17, 2021

wuwuzhijing commented on Sep 17, 2021

basic config

reproduction steps

If you need more info. , I will add later.

5 remaining items

mwwzbinf commented on Jun 20, 2023

dakhouya commented on Feb 20, 2024

brunoalr commented on Feb 20, 2024

JiahangWu commented on Mar 13, 2025

brunoalr commented on Mar 13, 2025

brunoalr commented on Mar 13, 2025

JiahangWu commented on Mar 13, 2025

brunoalr commented on Mar 13, 2025

JiahangWu commented on Mar 14, 2025

brunoalr commented on Jul 11, 2026

brunoalr commented on Aug 23, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions