Code::Blocks Forums
User forums => General (but related to Code::Blocks) => Topic started by: ElectroWizard on July 09, 2013, 09:26:58 pm
-
A "bad" plugin STILL may crash C::B... even using --safe-mode
--safe-mode does NOT really prevent the loading of plugin libraries...
Of course: we can disable the loading in several ways, such as renaming the lib to "Name.so--" (in linux/*nix...)
but
May I suggest creating some --safe-mode alike CLI flags:
--Disable-Load-All-Plugins to REALLY avoid loading ALL and ANY plugins libs
and
--Dont-Load-Plugin=<plugin1,plugin2...>
Thanks in advance
ElectroWizard
-
--Disable-Load-All-Plugins to REALLY avoid loading ALL and ANY plugins libs
100% useless option. The compiler is a plugin, so not loading it means useless C::B!
--Dont-Load-Plugin=<plugin1,plugin2...>
If you don't need a plugin it is better to
1. delete if from system
2. not build it in the first place (on windows as far as I know you can choose which plugins to install)
p.s. I agree that the plugin system should be redesigned, but it will wait awhile before it happens.
p.p.s. Use a debugger to track the problem and report it properly, don't try to workaround it. :)
-
100% useless option. The compiler is a plugin, so not loading it means useless C::B!
Nope, initially C::B was designed to be a powerful editor in this case, at least. Don't forget that you can even install C::B as an editor using the installer on Windows.
If disabled the compiler plugin makes C::B crash that this is a bug.
-
If disabled the compiler plugin makes C::B crash that this is a bug.
You can try for yourself, I don't think you could use C::B without a compiler...
-
You can try for yourself, I don't think you could use C::B without a compiler...
Will do, but it really used to work safely for a long time.