Forum > General

Access violation when opening Tools/Options

(1/4) > >>

Чебурашка:
Hello,
I noticed that with the lazarus shipped by debian 12 (lazarus 2.2.6) when I do Tools/Options I get an Access Violation, that seems related to the parsing of the jedi code formatter settings.

Once I encountered this issue, I tried to download from https://www.lazarus-ide.org/ the debian packages available there, in this case I tried with lazarus 3.2, but seems I get the same error.

Does anybody have the same problem?

TRon:
Debian bookworm x86_64 with mate & gtk here and no problem as described when running Lazarus 2.2.4, 2.2.6, 2.3, 3.0 or 3.2

Have you tried running Lazarus from the commandline ? Usually it emits a couple of lines when things go wrong and those lines might be able to tell more (so please copy-paste those lines to a message in this forum in case it emitted something useful).

It is possible to even obtain more (debug) information by providing commandline options to Lazarus. Type ./lazarus --help for detailed information for the argument --debug-enable and the options that it accepts.

JuhaManninen:

--- Quote from: Чебурашка on April 19, 2024, 12:27:34 pm ---... when I do Tools/Options I get an Access Violation, that seems related to the parsing of the jedi code formatter settings.

--- End quote ---
Nobody else seems to have the problem, thus it must be wrong/corrupt data in your local configuration.
Delete or rename your local configuration directory, by default ~/.lazarus
It will be recreated with default data when you start Lazarus again. Do you still get the error?

Чебурашка:
Thanks,
I came across this error with 2.2.6, then I downloaded and installed 3.2 as said and I got same error, and the latter seems a fresh install, so I guess .lazarus folrd was in kinda default state. 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.

Monday I will try again once I get to work, but is good that nobody else gets same error at least.

Martin_fr:
First backup all of your config files.

Then when you find the config file that causes the crash, and it has no personal data in it, please upload it. Then we can have a look to make sure such broken config give a proper error prompt, rather than a crash.

Navigation

[0] Message Index

[#] Next page