Robert Knight

That stacktrace is missing useful information unfortunately because as GDB's output says, it put the program back into the state it was in before the crash happened. Can you try...

> ~"Detaching from program: /home/kkk/\346\241\214\351\235\242/qthello/qthello, process 17943\n Ah, that's interesting. What is the full path to the 'qthello' program? There might be an issue with handling of non-ASCII characters. Can...

It looks to me like libQtInspector.so is not being linked with the appropriate protobuf libraries, or there is a mismatch between the header and that library that is being linked...

Windows support would be welcome but I'm afraid I don't have the time to work on it myself. For anyone who is interested in having a look, you'll need to...

> Is this already possible ? No, not at present. > If not, what would it take to add support for that ? You would need to find a way...

> I launch it as root as otherwise I got errors that it could not connect the process to inspect. Did you try both the `./qtinspector ` and `./qtinspector `...

Thank-you for including the logs in the bug report. The stacktrace shows that the crash is happening in code related to the Qt Resource System (qrc) which runs early on...

Did you build the application for Qt 4 or Qt 5? What version of Qt are you using in your test app?

Did you set the `USE_QT5` build option when building Qt Inspector? If not, please try that (see https://github.com/robertknight/Qt-Inspector/issues/19#issuecomment-487158737) and let me know if that works.

I think the syntax is `cmake -DUSE_QT5=ON`, but my memory may be fuzzy.