Forum > General
Access violation when opening Tools/Options
TRon:
--- Quote from: Чебурашка on April 20, 2024, 11:07:19 am ---To find out was was causing I did enable the extra logging and ran lazarus from bash, so I was ale to tell that it was due to jcf settings.
--- End quote ---
Glad to hear that you got that figured out.
--- Quote ---Monday I will try again once I get to work, but is good that nobody else gets same error at least.
--- End quote ---
It does make me wonder if the IDE should (be allowed to) crash when something is perhaps configured incorrectly or has become incompatible (*).
fwiw: by default the Lazarus configuration directory is installed 'globally' (usually in your user directory) and removing the package alone will not take care of these user configurations. That should be done manually. It is reason for a lot of people to use the pcp option to point the user configuration to a directory of your choice where it is possible to have multiple configuration directories for different versions of Lazarus (even when multiple versions of Lazarus are installed at the same time)
See also here about primary configuration path and here about multiple Lazarus (take special note of the lazarus.cfg file options).
(*) edit: ah I see I crossed Martin_fr's reaction where he suggest to upload the offending configuration files, most probably in an attempt to try prevent such crashes (?)
JuhaManninen:
@Чебурашка did not even try my suggestion which was to delete the local config dir. :(
--- Quote from: TRon on April 20, 2024, 11:24:35 am ---It does make me wonder if the IDE should (be allowed to) crash when something is perhaps configured incorrectly or has become incompatible (*).
--- End quote ---
It shouldn't crash. A debugger stacktrace would also help to find where it crashes. The whole IDE must then be compiled with debug info and run under a debugger.
TRon:
--- Quote from: JuhaManninen on April 20, 2024, 12:31:34 pm ---It shouldn't crash. A debugger stacktrace would also help to find where it crashes. The whole IDE must then be compiled with debug info and run under a debugger.
--- End quote ---
Thank you for the detailed in/con-formation JuhaManninen.
An upload of the offending configuration file(s) would be beneficial then as well as testing with a clean configuration directory with feedback whether that fixed the issue or not.
dbannon:
Hmm, I have to say that, as a committed "build lazarus from source" sort of guy, I find the idea of a default (and therefor reusable) configure directory part of the problem.
I really wonder if we should force a new config directory on a new install/build by default. Let the die hards over ride if they must. For most users, the few minutes it takes setup a new install is a small price to pay to avoid the advice "blow way your config" that is needed so often. I never reuse an old config.
Davo
TRon:
That is an interesting idea dbannon and made me think of something else.
Would it be a good idea to have a configuration directory that at least has the version number included (whether in separated sub-directories or something else). That way it would be possible to make it optional to 'import' an existing configuration while still being able to have them separated (by default).
On the other hand I wonder how many of us do have multiple installations of different versions installed. I often see people mention that they have installed multiple Lazarus' but of the same version (in which case my suggestion wouldn't stick and your idea would be better suited ?)
Navigation
[0] Message Index
[#] Next page
[*] Previous page