Code::Blocks Forums
User forums => General (but related to Code::Blocks) => Topic started by: CuteAlien on September 30, 2008, 08:00:24 am
-
Not sure if this is known already, didn't find it:
I renamed a folder which was used with in a project (outside c::b while c::b was closed). When trying to open that folder afterwards in the 'Projects' view c::b crashes.
Version was the current nightly build on Linux/Debian.
Btw. is this the correct forum for bugreports or should those be put into help or development?
-
I just tried to reproduce, but I was not able to.
Here is what I did:
- created a wxWidgets project (test) with wizard
- created a new dialog with wxSmith
- closed C::B
- created a subfolder test1
- moved the "NewDialog.*"-files into it
- opened C::B and fixed the paths, so I can open the dialog from within the OnAbout-function
- closed C::B
- renamed test1 to test2
- opened C::B
- opened folder test1 (no crash here)
- double-clicked on any file inside it
- got the error message, that the file could not be found (no crash !)
Can you provide a minimal project, where the error occurs, or tell exactly what you did, so that I can reproduce the crash.
It might also be helpful to post the part of the debugreport (that was hopefully created by C::B) that shows the stack.
That's everything inside "<stack>" and "</stack>".
The crash report can be found in /tmp/codeblocks_dbg.../" ( I don't know exactly at the moment).
Inside the folder there should be a file called "codeblocks.xml" containing the debugreport.
It can be written, even if C::B was not able to show it. Look for the one (if any) with the correct date/time of your crash.
-
Hm, yeah, didn't happen when I tried it again in another project.
Stack also doesn't look that helpful:
<stack>
<frame level="0" function="wxFatalSignalHandler" offset="00000026"/>
<frame level="1"/>
</stack>
I will try if I can reproduce it the next days (too busy right now watching some Milestone swishing past me).
edit: I tried a few more times now, but seems I'm not able to reproduce it :-(
-
Recently I got further crashes after renaming some files. This time after renaming them within C::B using the popup menu. First crash shortly after renaming, the next one after restarting c::b. Then it worked again. But once more it's not reproducable.
Is there maybe any sort of cache which is keeping it's data even after a restart? Just guessing here...
-
Hm, reviving this report as I just found out it still happens to crash sometimes on renaming. My system is by now a new Debian Lenny with a nighly build (svn 5456) of c::b.
This time the crash happened when I removed the same 2 files from 2 different sub-projects, renamed them outside (with hg rename) and it crashed on trying to add the renamed files back to the first project. Once more I couldn't reproduce it on trying again. Only thing I'm sure of is that it has to do something with renaming...
Crashreport contained no <stack> at all this time.