Bruno Alexandre Rosa

I also created https://github.com/OpenImageDebugger/OpenImageDebugger/issues/27 to better deal with the dependency versions that are currently supported.

See https://lldb.llvm.org/use/python-reference.html

We don't have automated tests yet, but I think this a good candidate to become one. Do you mind sharing a minimal example that leads to a crash?

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

@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 I can help :) I need more information first: - OID's commit hash - operating system and version - gdb version - lldb version - python2 and python3 versions...

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

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

Hi @onyx22574, first you need to implement some interfaces to correctly parse the image class(es) you want to plot, see this post here https://csantosbh.wordpress.com/2016/10/15/configuring-gdb-imagewatch-to-visualize-custom-buffer-types/. Long story short, OID needs to...

You can also check how this is done for opencv types here: https://github.com/OpenImageDebugger/OpenImageDebugger/blob/main/resources/oidscripts/oidtypes/opencv.py