User forums > Using Code::Blocks
CodeBlocks crashed when opening source file
stahta01:
--- Quote from: Grit Clef on September 01, 2023, 11:34:07 am ---GCC 13.1.0, Windows 7 32bit
--- End quote ---
I think he needs the exact compiler information and did you use the exact same compiler to build both CB and the plugins?
Edit: Oops, I just realized libgcc_s_dw2 is not a threading DLL; but, dwarf version of gcc lib
--- Code: ---5FA90000-5FB57000 libgcc_s_dw2-1.dll
70CF0000-70CFE000 libmcfgthread-1.dll 1.5.0.0
--- End code ---
Tim S.
Pecan:
I've now spent nearly 6 hours trying to find a means to associate the clangd_client crash address with a source line.
I've failed with nm.exe, Dependentcies.exe, Addr2line.exe, Addr2lineUI.exe. None report anything usable.
The only action now is to use the devel debugging version of clangd_client in the output32 directory so that the crash report contains the source line.
@Grit Clef
Rename your ouput32 plugin version of clangd_client.dll to clangd_client.dll.bak.
Make sure the clangd_client was compiled with the -g compiler options in order to get debugging info.
Copy the clangd_client.dll from the devel32\share\codeblocks\plugins directory to the output32\share\codeblocks\plugin directory.
Do not run ./update32, because it will strip out the debugging info.
BTW, those directories may have a slightly different name, like devel32_64, output32_64, etc.
Try to recreate the crash.
When it crashes, the .rpt file should contain the source line number of the crash.
Thanks
Grit Clef:
Oops! I replaced the clangd_client dll with the debug version, then started CB. I opened yesterday's project, and CB showed me a dialog to provide a correct clangd position. Strange, because I havn't changed my clangd and all the other things. Then, when I gave CB the original position, it told me that this clangd was incorrect. I clicked Yes, and a MSVC Runtime Error occured(No RPT file). That was related to libstdc++-6.dll. Then CB stopped response. I restarted it, everything returned to normal, but I can't recreate yesterday's crash, either.
Grit Clef:
Also, I tried back the release version, now it can't make that problem reappear, either.
Pecan:
--- Quote from: Grit Clef on September 02, 2023, 10:44:18 am ---Also, I tried back the release version, now it can't make that problem reappear, either.
--- End quote ---
Ok, but just leave the devel version of clangd_client.dll in your runtime directory (output32). Maybe the crash will occur some time in the future and we'll catch the source line number in the .rpt file.
If you update CodeBlocks, please remember to hand copy the devel version of clangd_client.dll to your output32 directory after you run ./update32_64(or whichever one you use).
It appears that you're using a compiler different from the one the rest of us use. You might want to go to the nightly forum thread and download the compiler ususally used to compile codeblocks. It has a link for the compiler.
Of course the wxWidgets linked with CodeBlocks both have to be compiled with the same compiler.
https://forums.codeblocks.org/index.php/topic,25516.msg173682.html#msg173682
Thanks for the report and for working to identify this problem.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version