Bug #19121 2013-09-11 07:48
koonschi
Segmentation fault when reparsing a file
I'm running the latest svn build compiled from source with contrib plugins, on kubuntu 13.04 64 bit.
I have the 'update parser while typing' setting enabled, and I get a segmentation fault that seems to occur when codeblocks tries to reparse a file. I also press CTRL + S a lot, if that helps, as I had the impression that this might trigger a reparse, too.
This is the last console output before the crash:
Parser::Reparse : The Parser is not done. > Reasons:
- still batch parse files to parse
NativeParser::OnParserStart(): Starting re-parsing for project 'SpaceServer'...
Project 'SpaceServer' parsing stage done (1464 total parsed files, 33649 tokens in 0 minute(s), 0.018 seconds).
ClassBrowser::OnThreadEvent(): Updating class browser...
ClassBrowser::OnThreadEvent(): Class browser updated.
Reparsing when typing for editor /home/koonschi/Documents/devel/space/SpaceServer/Database/FactionDatabase.cpp
NativeParser::OnParserStart(): Starting re-parsing for project 'SpaceServer'...
Project 'SpaceServer' parsing stage done (1464 total parsed files, 33649 tokens in 0 minute(s), 0.018 seconds).
ClassBrowser::OnThreadEvent(): Updating class browser...
ClassBrowser::OnThreadEvent(): Class browser updated.
Reparsing when typing for editor /home/koonschi/Documents/devel/space/SpaceServer/Database/FactionDatabase.cpp
NativeParser::OnParserStart(): Starting re-parsing for project 'SpaceServer'...
codeblocks: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Segmentation fault (core dumped)
- Category
- Plugin::CodeCompletion
- Group
- Platform:Linux
- Status
- Open
- Close date
- Assigned to
History
I think CC(codecompletion plugin) has a lot of bugs related to wxString. Because wxString under wxWidgets 2.8.12 use its own implementation which does not use atomic reference counters. Even we have a lot of lockers to protect the tokentree or other things, but that not enough as I see.
I can't say much about the crash bug, because I don't see how the bug happens...sorry.