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

[openimagedebugger]

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

[YihaoWEI]

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

[mwwzbinf]

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

[dakhouya]

@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

[brunoalr]

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.

[github-actions]

Stale issue message

[wuwuzhijing]

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

Any ideas?

[brunoalr]

@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

[wuwuzhijing]

@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.

[wuwuzhijing]

@brunoalr
Can you figure out the problem?

[brunoalr]

@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 :) )

[wuwuzhijing]

@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

1. 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

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

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

[brunoalr]

Thanks for the information!

settings
source /mypath/OpenImageDebugger/oid.py

I tried to reproduce it on my machine and I get a similar error messages when calling source oid.py via bash.

source /tmp/OpenImageDebugger/oid.py 
/tmp/OpenImageDebugger/oid.py:5: command not found: \nOpen Image Debugger entry point. Can be called with --test for opening the plugin\nwindow with a couple of sample buffers; otherwise, should be invoked by the\ndebugger.\n

^C^C^C/tmp/OpenImageDebugger/oid.py:17: no matches found: os.path.dirname(os.path.realpath(__file__))
/tmp/OpenImageDebugger/oid.py:18: number expected

In this case, source is a gdb command instead of a *sh command. More info here: https://sourceware.org/gdb/onlinedocs/gdb/Command-Files.html

Two things I want to verify:

• Can you run cat ~/.gdbinit and paste the output here?
• After reproduction step 6) can you call source /mypath/OpenImageDebugger/oid.py on the gdb console? (I am not familiar with the exact steps to access the gdb console inside Visual Studio)

[wuwuzhijing]

@brunoalr
Thank you.

cat ~/.gdbinit

gdb console out after 6)

[brunoalr]

@wuwuzhijing this seems to be right. Were you able see the GUI afterwards?

As far as I remember, there was no need for IDE hooks for OID to work with VSCode, but it is been a while. If I get some free time I will try to debug the TestBench under VSCode - usually I use gdb from the CLI :)

[wuwuzhijing]

@brunoalr
NO GUI.
I can only try CLI before you figure out the problem of this tool using under VSCode.

[wuwuzhijing]

@brunoalr
I still wander, now that the source /path/oid.py works unnormal, how did you make it from the CLI? Can you paste a brief step instruction?

[brunoalr]

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