User forums > Help

Several show-stopping problems

<< < (4/6) > >>

klight:
I can also confirm it's fixed.
Thank you!

ikolev:
Big thanks from me too. It's working now.

Another good news is that C::B has not crashed on me yet since I installed the nightly build in a clean folder. I guess this is worth mentioning somewhere (e.g. in some instructions for installing the nightly builds). Unless it is mentioned and I have missed it.

takeshimiya:

--- Quote from: ikolev on March 13, 2006, 09:33:17 pm ---Big thanks from me too. It's working now.

Another good news is that C::B has not crashed on me yet since I installed the nightly build in a clean folder. I guess this is worth mentioning somewhere (e.g. in some instructions for installing the nightly builds). Unless it is mentioned and I have missed it.

--- End quote ---

What would be good to understand is why the crashes.
The configuration can't be, as it was saved in the registry.
The old lexers/resources/etc shouldn't crash C::B, because they hadn't changed much, and all the code is backwards compatible.

The only thing that could produce the crash would be old shared libraries.

Like old plugins with different name or not in new versions (as the svn plugin).
But if that's the case, loading plugins made for a previous SDK shouldn't load, as they are versioned.

The other cause could be that the wxWidgets dll shipped with RC2 was another version (2.6.1?).
But if that's the case, we should start building wxWidgets as wxmsw262u instead of wxmsw26u.
Or another option could be to check upon C::B load at runtime, if the main app and plugins were compiled against the same configuration&version of wxWidgets dll.

So, what could be the problem?

thomas:

--- Quote ---The old lexers/resources/etc shouldn't crash C::B, because they hadn't changed much, and all the code is backwards compatible.
--- End quote ---
As it happens, those are the likely reason.

--- Quote ---The only thing that could produce the crash would be old shared libraries.
Like old plugins with different name or not in new versions (as the svn plugin).
--- End quote ---
No, Takeshi.

takeshimiya:

--- Quote from: thomas on March 13, 2006, 10:57:56 pm ---
--- Quote ---The old lexers/resources/etc shouldn't crash C::B, because they hadn't changed much, and all the code is backwards compatible.
--- End quote ---
As it happens, those are the likely reason.

--- End quote ---

It is spotted which are exactly?
I don't understand which one could be, as most resources are loaded from the zips, and all those are overwritten by new versions because they have the same name. And the lexers have the same name too.

Doing a diff of all files between RC2 and HEAD, gives the next sensible files missing in HEAD:

CodeBlocks/share/CodeBlocks/plugins/cbDragScroll.dll
CodeBlocks/share/CodeBlocks/plugins/FileTabMenu.dll
CodeBlocks/share/CodeBlocks/plugins/svn.dll
CodeBlocks/share/CodeBlocks/svn.zip
CodeBlocks/mingwm10.dll
CodeBlocks/wxmsw26_gcc_cb.dll

So those are the ones that could introduce a problem, the rest are overwritten by same-name files.

That is, unless ikolev had click "don't overwrite files" when uncompressing Nighlty over RC2.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version