Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

crashes after --clear-configuration

(1/1)

tiwag:
a short description, what i've done
(i hope i can remember all step's ;-)

i worked on customizing a new compiler set for
IAR Hitachi H8 compilers, which i got working.

when i edited the regexes for error's and warning's,
i deleted some of the for the IAR toolchain irrelevant
error entries, so that only compiler error & warnings
and linker errors have been left.

all worked as expected after a while.

BUT !!!
later i switched to another project, which is using the
GCC toolchain and  i took notice, that even in this compiler
configuration the error & warning entries,
which i wanted to delete only for the IAR toolchain, were deleted !

damned i thought, and exported the registry entries for the
newly created IAR toolchain

and fired up C::B with --clear-configuration

that was not very wise ! ;-)

after that, C::B crashed at each start with a GPF, this could only be resolved with a procedure, described a few times by others here in the forum, namely
by installing C::B 1.0 beta final, and starting the src\devel version with the debugger and then run an update.bat

from this time on, C::B from the src\output could be run without crash again, but it nags me everytime during startup, to acknowledge which compiler should be the default compiler.
It doesn't remember my choice during subsequent restarts.

Where is this info stored ? can i manually add a registry entry to suppress this dialog box at each start of C::B

in the registry there exists in
HKEY_CURRENT_USER\Software\Code::Blocks\Code::Blocks v1.0\compiler_gcc
DWORD default_compiler = 0x00

but it seem's not to be right entry ?


thanks
--tiwag

mandrav:

--- Quote ---after that, C::B crashed at each start with a GPF
--- End quote ---

Just fixed it in CVS.


--- Quote ---from this time on, C::B from the src\output could be run without crash again, but it nags me everytime during startup, to acknowledge which compiler should be the default compiler.
It doesn't remember my choice during subsequent restarts.
--- End quote ---

I tested it and I can't reproduce this.
Keep in mind that the window showing at startup listing the detected compilers, is only shown if the auto-detection is ran. Not to select the default compiler but to show you the results of its auto-detection.
If it keeps appearing, it means that at least one compiler has a blank master path setting...


--- Quote ---can i manually add a registry entry to suppress this dialog box at each start of C::B
--- End quote ---

As said, make sure all compilers have their master path set (yes, even those you don't have installed).


--- Quote ---in the registry there exists in
HKEY_CURRENT_USER\Software\Code::Blocks\Code::Blocks v1.0\compiler_gcc
DWORD default_compiler = 0x00
--- End quote ---

This is the compiler's index. '0' is GCC.

Yiannis.

tiwag:

--- Quote from: mandrav ---
Keep in mind that the window showing at startup listing the detected compilers, is only shown if the auto-detection is ran. Not to select the default compiler but to show you the results of its auto-detection.
If it keeps appearing, it means that at least one compiler has a blank master path setting
...
As said, make sure all compilers have their master path set (yes, even those you don't have installed).

--- End quote ---


thanks,
the missing master-path was causing it ,
the ever appearing default compiler dialogue is solved now !


the only thing left is the mysterious deleting of regex strings of another compiler than the selected one. it must have to do something with the sometimes not properly working of the workspace saving and/or modified project saving.
Also during several editing sessions of the error/warning regexes, i had to scroll up/down in the list of regexes, until the last modification was taken as modified and stored in the registry.
If i only modify one regex (e.g. linker error) and press OK button, it isn't updated, but when i select another entry in the listbox after modifying the linker error (eg. compiler error) and then again select the linker error, it shows me the updated regex and stores it also in the registry after pressing the OK button.

Something mysterious is happening, when deleting regexes complete from the listbox, and NOT editing anything, but i didn't test it complete, because i have to work right now with the H8 hitachi project, my customer want's to have a working embedded system on monday morning ;-)

mandrav:

--- Quote ---the only thing left is the mysterious deleting of regex strings of another compiler than the selected one.
--- End quote ---

I 'm looking at it right now ;)

Yiannis.

mandrav:

--- Quote ---If i only modify one regex (e.g. linker error) and press OK button, it isn't updated, but when i select another entry in the listbox after modifying the linker error (eg. compiler error) and then again select the linker error, it shows me the updated regex and stores it also in the registry after pressing the OK button.
--- End quote ---

Yes, this is a bug and was just fixed in CVS.


--- Quote ---the only thing left is the mysterious deleting of regex strings of another compiler than the selected one. it must have to do something with the sometimes not properly working of the workspace saving and/or modified project saving.
--- End quote ---

This, I can't reproduce. I tried everything. If you find a way to reproduce it, please post it...

Yiannis.

Navigation

[0] Message Index