Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Code completion using LSP and clangd
ollydbg:
--- Quote from: Pecan on March 02, 2024, 06:09:38 pm ---Clangd Code Action (aka "fix available") is enabled from Head rev 13484.
Right-click any LSP log message containing "fix available" and select "Apply fix available" from the context menu.
--- End quote ---
This is a really nice feature! Good work!!! I will try it soon.
gd_on:
I have problems with this new svn 13484 version, even after a full C::B rebuild. I use wxWidgets 3.2.4 for C::B on a Windows 11 64 bits.
C::B compiles normally. executable launches normally too, but when I try to open a project, I obtain an unhandled exception. I can try to continue, but C::B does not work as it should.
I have a rpt file which indicates problems within wxsmithlib.dll, but strangely no references to clangd plugin, but it's certainly this plugin which causes the problem. I had no such problem with my previous svn 13482.
I'm on windows 11 fully updated. I use gcc, clangd,... form msys2 installation, fully updated too.
If I disable clangd plugin and use standard codecompletion, it works correctly.
May be, it's something wrong on my side, but until now, I have not found the problem.
gd_on
Pecan:
@gd_on
Please copy the newly built clangd_client.dll from the devel folder to the output folder (since the devel version has debugger info) and try again.
The exception should be caught if you'll respond with "stop" to the exception notice and the .rpt file should have a backtrace.
Alternatively, you could run coldeblocks in the debugger and repond "stop" to the exception and the debugger will stop on the exception line.
Make sure that your debugger options are set to "catch c++ exceptions" and that you compiled all of codeblocks with the -g compiler option (Settings/Globals cb_release_type).
Thanks.
gd_on:
Very strange ... This morning, after a new full rebuild, it works, no unhandled exception ! I cross my fingers.
gd_on
PS : my problem was apparently that I use my own version of cbp to build clang plugin. Normally, it is compatible with Pecan's one, except that I have no option -g and use -std=gnu++20 instead of -std=gnu++11.
If I restore those two options, as in Pecan's .cbp, it's OK.
Pecan:
--- Quote from: gd_on on March 04, 2024, 10:26:23 am ---Very strange ... This morning, after a new full rebuild, it works, no unhandled exception ! I cross my fingers.
gd_on
PS : my problem was apparently that I use my own version of cbp to build clang plugin. Normally, it is compatible with Pecan's one, except that I have no option -g and use -std=gnu++20 instead of -std=gnu++11.
If I restore those two options, as in Pecan's .cbp, it's OK.
--- End quote ---
@gd_on
That's interesting. Looks like I'd better do some testing with gnu++20.
Thanks for reporting that.
Please tell me the version of gcc and clangd you're using so I can exactly mirror your evnvironment. Tell me also anything else you think I should mirror?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version