Forum > General

Lazarus crashing at startup

(1/4) > >>

I have laz  2.0.10 on deb 11.5.
It is some days that Lazarus crashes and dies after I click the menu button to launch it  (sometimes, not always).
It was about 2 months I am using it normally.
The suspect is that all started when I tried to put a link to lazarus on the below panel (widget).

Is there some log I can see to do some inspection?

if you are using Linux you can start it from the command line. A stream of log data ....

If you are using Windows, its possible to redirect that output to a file, start it (maybe from a shortcut) with a commandline option like this

--- Code: -----debug-log=SOME.LOG
--- End code ---

Make sure SOME.LOG will be written to somewhere you have write permission.

If you are using OSF on an Alpha System, then, sorry, you are on your own.  (thats a soft hint to tell us what your system is when you post such a message).



--- Quote from: dbannon on December 04, 2022, 10:58:48 am ---(thats a soft hint to tell us what your system is when you post such a message).

--- End quote ---

David, thanks for the suggestions, I will use for sure.

My system was written in the post:

--- Quote from: tt on December 04, 2022, 10:30:09 am ---I have laz  2.0.10 on deb 11.5.

--- End quote ---

But maybe deb is a short of debian and was not 100% clear... sorry..

No tt, that should be entirely clear to me and I apologize unreservedly !

So, start your lazarus from a command line. You will see quite a lot of whats happening as it starts up.

2.0.10 is pretty old, thats an issue with long life distros  like bullseye (I am assuming, sigh, that yours is installed from the Debian Repo ?)  While being old is not the cause of your problem (again, I assume) newer is always better !

There are current FPC and Lazarus in backports, but, honestly, I would strongly recommend either getting it from the official Lazarus download or, my preference, build Lazarus from source, honestly, its really easy ! At the end of the install, you will feel you really own the install, you understand how it all works !  Very liberating...


EDIT: You can, if you like, also add a command line switch to your start menu.  But better, maybe, to use a small script that will capture each restart, deleting the previous one. Thats way, if it does not crash every time, you can use it until it does, then swoop down on the log file.

I created a small startup sh to add debugging to lazarus.

--- Code: Text  [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---user_tt@user_tt-development:~$ cat /usr/bin/startlazarus-user_tt #!/bin/sh # /usr/bin/lazarus-ide is the link to the actual startup program in debian 11.5/usr/bin/lazarus-ide  --debug-log=lazarus-ide-debug.log --debug-enable=DBG_VERBOSE,DBG_WARNINGS,DBG_STATE,DBG_EVENTS,DBG_STATE_EVENT,DBG_DATA_MONITORS,DBG_DISASSEMBLER,DBG_LOCATION_INFO,SYNMOUSEEVENTS,SRCED_LOCK,SRCED_OPEN,SRCED_CLOSE,SRCED_PAGES,DBG_CMD_ECHO,DBG_CMD_ECHO_FULL,DBGMI_TYPE_INFO,DBGMI_TIMEOUT_DEBUG,DBG_THREAD_AND_FRAME,DBGMI_QUEUE_DEBUG,DBGMI_STRUCT_PARSER,FPDBG_DWARF_ERRORS,FPDBG_DWARF_WARNINGS,FPDBG_DWARF_VERBOSE,FPDBG_DWARF_VERBOSE_LOAD,FPDBG_DWARF_SEARCH,FPDBG_DWARF_DATA_WARNINGS,DBG_ERRORS $@ & 
I attached two logs one with a crash and one with a normal open/close of lazarus. These logs where produced within the same minute using the same startup lpi, and without any modification to the lpi or to any unit of it. Very strange.

If someone can tell I would appreciate a lot.


[0] Message Index

[#] Next page

Go to full version