I had a working debugger options dialog, but now, after cvs update, it's broken. I have a segfault. Here is gdb output:

(gdb) run
Starting program: /usr/share/lazarus/lazarus
NOTE: editor options config file not found - using defaults NOTE: miscellaneous options file not found - using defaults NOTE: codetools config file not found - using defaults TMainIDE.DoNewProject A
TMainIDE.DoNewEditorFile A NewFilename=
TPascalParserTool.BuildTree B OnlyIntf=FALSE project1.lpr [TCustomFormEditor.CreateComponent] Class='TFORM'
TPascalParserTool.BuildTree B OnlyIntf=FALSE project1.lpr TMainIDE.DoNewEditorFile end unit1.pas
TMainIDE.DoNewProject end 0
Form streaming "TDEBUGGEROPTIONSFORM" error: Error while reading chkClearLogOnRun.DragCursor: Invalid property value

Program received signal SIGSEGV, Segmentation fault. $080d08e3 in TDEBUGGEROPTIONSFORM__ADDEXCEPTIONLINE (AEXCEPTION=$405de544, ANAME=$83c2563, this=$4048eb64) at debugoptionsfrm.pas:128 128 idx := clbExceptions.Items.AddObject(AName, AException);

If I could find the default config file I'd start over, but I don't know where it is. I've renamed the local .lazarus file to no avail. Thanks.

I had a working debugger options dialog, but now, after cvs update, it's broken. I have a segfault. Here is gdb output:

Reading the form from the lazarus resource fails because of the DragCursor property. Therefore the CheckListBox isn't created.

Mattias regenerated the lrs and lfm to remove the named color constant, but the constant for DragCursor remained. It is also found in other regenerated forms, which used be OK, because they were created with lazarus compiled with a pre 1.9 fpc.

IMHO there are three solutions to these kind of problems.
- Only check in forms (.lrs and .lfm files) created with lazarus compiled with fpc 1.0.x.
- Say that fpc 1.9.1 with a date later than 15-12-2003 is the required compiler for lazarus.
- Fix (or better enhance) fpc 1.0.x to support reading named constant values and put an new compiler rpms on the website.

IMHO the present situation with only the default properties stored is too error prone.

Regards,
Vincent.
Ken, sorry for the inconvenience.