From nc-gaertnma at netcologne.de Thu Nov 1 08:46:26 2018 From: nc-gaertnma at netcologne.de (Mattias Gaertner) Date: Thu, 1 Nov 2018 08:46:26 +0100 Subject: [Lazarus] Lazarus Release Candidate 2 of 2.0 Message-ID: <20181101084626.39151b2e@limapholos.matflo.wg> The Lazarus team is glad to announce the second release candidate of Lazarus 2.0. This release was built with FPC 3.0.4. The previous release Lazarus 1.8.4 was built with FPC 3.0.4 as well. Here is the list of fixes for Lazarus 2.0.x: http://wiki.freepascal.org/Lazarus_2.0_fixes_branch Here is the list of changes for Lazarus and Free Pascal: http://wiki.lazarus.freepascal.org/Lazarus_2.0.0_release_notes http://wiki.lazarus.freepascal.org/User_Changes_3.0.4 The release is available for download on SourceForge: http://sourceforge.net/projects/lazarus/files/ Choose your CPU, OS, distro and then the "Lazarus 2.0RC2" directory. Checksums for the SourceForge files: http://www.lazarus-ide.org/index.php?page=checksums#2_0_0RC2 Minimum requirements: Windows: 2k, XP, Vista, 7, 8, 8.1 and 10, 32 or 64bit. FreeBSD/Linux: gtk 2.8 for gtk2, qt4.5 for qt, qt5.6 for qt5, 32 or 64bit. Mac OS X: 10.5 to 10.12; Carbon (32bit), Cocoa (64bit, beta), qt and qt5 (32 or 64bit). The svn tag is http://svn.freepascal.org/svn/lazarus/tags/lazarus_2_0_0_RC2 For people who are blocked by SF, the Lazarus releases from SourceForge are mirrored at: ftp://ftp.freepascal.org/pub/lazarus/releases/ and later at (after some time for synchronization) http://mirrors.iwi.me/lazarus/ == Why should everybody (including you) test the release candidate? == In the past weeks the Lazarus team has stabilized the 2.0 fixes branch. The resulting 2.0RC2 is now stable enough to be used by any one for test purposes. However many of the fixes and new features that where committed since the release of 1.8 required changes to the code of existing features too. While we have tested those ourself, there may still be problems that only occur with very specific configurations or one project in a million. Yes, it may be that you are the only person with a project, that will not work in the new IDE. So if you do not test, we can not fix it. Please do not wait for the final release, in order to test. It may be too late. Once the release is out we will have to be more selective about which fixes can be merged for further 2.0.x releases. So it may be, that we can not merge the fix you require. And then you will miss out on all the new features. == How to test == Download and install the 2.0 RC2. - On Windows you can install as a 2ndary install, that will not affect your current install: http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus - On other platforms, if you install to a new location you need to use --primary-config-path In either case you should make backups. (including your primary config) Open your project in the current Lazarus (1.8.x), and use "Publish2 Project" from the project menu. This creates a clean copy of your project. You can then open that copy in the RC2. Please test: - If you can edit forms in the designer - rename components / change properties in Object inspector / Add new events - Add components to form / Move components on form - Frames, if you use them - If you can navigate the source code (e.g. jump to implementation) - Auto completion in source code - Compile, debug and run - Anything else you use in your daily work Mattias From jmlandmesser at gmx.de Thu Nov 1 11:17:33 2018 From: jmlandmesser at gmx.de (John Landmesser) Date: Thu, 1 Nov 2018 11:17:33 +0100 Subject: [Lazarus] Loading an image to a mysql blob In-Reply-To: <1540987546.8666.9.camel@haimann.us> References: <1540987546.8666.9.camel@haimann.us> Message-ID: Am 31.10.18 um 13:05 schrieb Terry A. Haimann via Lazarus: > I tried loading an image into a Medium Blob.  The image uploads and > shows up on my form, but when I click post on my DbNavigator the > program gives me an access violation. > > Here is the source code: > > procedure TPropertyForm.ImgButClick(Sender: TObject); > Var >   MyImageFile, MyDir:                              String; > begin >      MyImageFile := '/'; >      if OpenDialog1.Execute then >      begin >           MyImageFile := OpenDialog1.Filename; >      end; >      DbPropImg.Picture.Jpeg.LoadFromFile(MyImageFile); > > End; > > Am I missing something I have to do?  The blob should be large enough, > they are supposed to be able to hold 16 Meg and the jpegs are running > about 2 - 3 meg.  I am running Mint 18.3, using Mysql 5.7.22 and using > ZeosDBO. > > Terry Haimann .. perhaps a Dataset.edit before DbPropImg.Picture.Jpeg.LoadFromFile(MyImageFile); DbPropImg.Picture.Jpeg.LoadFromFile(MyImageFile); From aaa5500 at ya.ru Thu Nov 1 16:59:40 2018 From: aaa5500 at ya.ru (AlexeyT) Date: Thu, 1 Nov 2018 18:59:40 +0300 Subject: [Lazarus] App UI scaling idea Message-ID: I saw in some apps an option: scale UI - 100%..300%. Eg in Telegram. Can it be idea for LCL? Can u add global variable, GlobalScalingPercents, which is affected by OS PixelPerInch, but also can be affected by app? App can give option like in Telegram. -- Regards, Alexey From terry at haimann.us Thu Nov 1 18:51:03 2018 From: terry at haimann.us (Terry A. Haimann) Date: Thu, 01 Nov 2018 12:51:03 -0500 Subject: [Lazarus] Loading an image to a mysql blob In-Reply-To: References: <1540987546.8666.9.camel@haimann.us> Message-ID: <1541094663.13419.3.camel@haimann.us> I had already tried that.  I clicked on edit from the dbnavigator, uploaded the image and clicked post.  That is when the program would crash. I have taken the program a different route, gotten rid of the blob and replaced it with a varchar.  The varchar now has the filename of the jpeg.  It's not fast, but it works. Terry On Thu, 2018-11-01 at 11:17 +0100, John Landmesser via Lazarus wrote: > Am 31.10.18 um 13:05 schrieb Terry A. Haimann via Lazarus: > > > > I tried loading an image into a Medium Blob.  The image uploads and > > shows up on my form, but when I click post on my DbNavigator the > > program gives me an access violation. > > > > Here is the source code: > > > > procedure TPropertyForm.ImgButClick(Sender: TObject); > > Var > >    MyImageFile, MyDir:                              String; > > begin > >       MyImageFile := '/'; > >       if OpenDialog1.Execute then > >       begin > >            MyImageFile := OpenDialog1.Filename; > >       end; > >       DbPropImg.Picture.Jpeg.LoadFromFile(MyImageFile); > > > > End; > > > > Am I missing something I have to do?  The blob should be large > > enough, > > they are supposed to be able to hold 16 Meg and the jpegs are > > running > > about 2 - 3 meg.  I am running Mint 18.3, using Mysql 5.7.22 and > > using > > ZeosDBO. > > > > Terry Haimann > .. perhaps a Dataset.edit before > > DbPropImg.Picture.Jpeg.LoadFromFile(MyImageFile); > > > > DbPropImg.Picture.Jpeg.LoadFromFile(MyImageFile); > From zmuogs at gmail.com Thu Nov 1 22:42:31 2018 From: zmuogs at gmail.com (=?UTF-8?Q?Valdas_Jank=c5=abnas?=) Date: Thu, 1 Nov 2018 23:42:31 +0200 Subject: [Lazarus] Can't compile Lazarus on Raspberry Pi3 using fpc 3.3.1 and Larzarus r>57100 Message-ID: <562cdfe8-b9ac-cc9b-c897-46926ee0c825@gmail.com> Hello, I have Raspberry Pi3 B with fresh Raspbian Stretch (image 2018-10-09) on it. I need FPC trunk because a Bug (https://bugs.freepascal.org/view.php?id=32005) so I followed these instructions and successfully compiled FPC from trunk r40152 (using 'OPT="-dFPC_ARMHF"'): https://bigdanzblog.wordpress.com/2015/06/13/compiling-the-latest-lazarusfree-pascal-for-raspberry-pi/ I used same instructions to download and compile Lazarus 2.1.0 from trunk from SVN, but I cant compile it because compilation aborts with lines: gtk2proc.inc(4631,15) Fatal: Internal error 200108231 Fatal: Compilation aborted Makefile:2956: recipe for target '../lcl.ppu' failed make[3]: *** [../lcl.ppu] Error 1 make[3]: Leaving directory '/usr/local/lazarus/source/lcl/interfaces/gtk2' Makefile:3293: recipe for target 'gtk2_all' failed make[2]: *** [gtk2_all] Error 2 make[2]: Leaving directory '/usr/local/lazarus/source/lcl/interfaces' Makefile:4460: recipe for target 'interfaces' failed make[1]: *** [interfaces] Error 2 make[1]: Leaving directory '/usr/local/lazarus/source/lcl' Makefile:3243: recipe for target 'lcl' failed make: *** [lcl] Error 2 For info compilation starts with lines: # make all OPT="-dFPC_ARMHF" make -C packager/registration make[1]: Entering directory '/usr/local/lazarus/source/packager/registration' /bin/rm -f ../units/arm-linux/fcllaz.ppu /usr/local/bin/ppcarm -MObjFPC -Scghi -O1 -g -gl -l -vewnhibq -Fu. -Fu/usr/local/lib/fpc/3.3.1/units/arm-linux/rtl -FE. -FU../units/arm-linux -dFPC_ARMHF -darm fcllaz.pas Hint: (11030) Start of reading config file /etc/fpc.cfg Hint: (11031) End of reading config file /etc/fpc.cfg Free Pascal Compiler version 3.3.1 [2018/11/01] for arm Copyright (c) 1993-2018 by Florian Klaempfl and others (1002) Target OS: Linux for ARMHF (3104) Compiling fcllaz.pas ..... I tried various revisions (erase previous revision completely -> checkout to different revision): - cannot compile: latest, 59000, 58500, 58000, 57500, 57200 - compiles without errors: 57100 (and I can start it: main window header shows v1.9.0), 57000 (checked two times) How resolve this problem and have latest Lazarus from trunk? -- Valdas Jankūnas From ganmax at narod.ru Thu Nov 1 22:47:26 2018 From: ganmax at narod.ru (Maxim Ganetsky) Date: Fri, 2 Nov 2018 00:47:26 +0300 Subject: [Lazarus] Can't compile Lazarus on Raspberry Pi3 using fpc 3.3.1 and Larzarus r>57100 In-Reply-To: <562cdfe8-b9ac-cc9b-c897-46926ee0c825@gmail.com> References: <562cdfe8-b9ac-cc9b-c897-46926ee0c825@gmail.com> Message-ID: 02.11.2018 0:42, Valdas Jankūnas via Lazarus пишет: > gtk2proc.inc(4631,15) Fatal: Internal error 200108231 This line indicates FPC bug. -- Best regards, Maxim Ganetsky mailto:ganmax at narod.ru From zmuogs at gmail.com Thu Nov 1 23:01:16 2018 From: zmuogs at gmail.com (=?UTF-8?Q?Valdas_Jank=c5=abnas?=) Date: Fri, 2 Nov 2018 00:01:16 +0200 Subject: [Lazarus] Can't compile Lazarus on Raspberry Pi3 using fpc 3.3.1 and Larzarus r>57100 In-Reply-To: References: <562cdfe8-b9ac-cc9b-c897-46926ee0c825@gmail.com> Message-ID: <724782ab-701a-4adc-19f0-9b5c6584b8f1@gmail.com> 2018-11-01 23:47, Maxim Ganetsky via Lazarus rašė: > 02.11.2018 0:42, Valdas Jankūnas via Lazarus пишет: >> gtk2proc.inc(4631,15) Fatal: Internal error 200108231 > > This line indicates FPC bug. > Reported: https://bugs.freepascal.org/view.php?id=34495 -- Valdas Jankūnas From l at c-m-w.me.uk Sat Nov 3 14:37:20 2018 From: l at c-m-w.me.uk (C Western) Date: Sat, 3 Nov 2018 13:37:20 +0000 Subject: [Lazarus] Lazarus Release Candidate 2 of 2.0 In-Reply-To: <20181101084626.39151b2e@limapholos.matflo.wg> References: <20181101084626.39151b2e@limapholos.matflo.wg> Message-ID: On 01/11/2018 07:46, Mattias Gaertner via Lazarus wrote: > The Lazarus team is glad to announce the second release candidate of > Lazarus 2.0. > I am still seeing the error on loading a (specific) package with missing dependencies, but I have been able to do some debugging to track down the error. It is clear I should have specified the platform in my original message, as I think the error will not manifest on windows. I think the error is in packager/packagesystem.pas: 933    function TLazPackageGraph.OpenDependencyWithPackageLink( 934      Dependency: TPkgDependency; PkgLink: TPackageLink; ShowAbort: boolean 935      ): TModalResult; 942    begin 943      NewPackage:=nil; 944      XMLConfig:=nil; 945      BeginUpdate(false); 946      try 947        AFilename:=PkgLink.GetEffectiveFilename; 948        if pvPkgSearch in Verbosity then 949          debugln(['Info: (lazarus) Open dependency: trying "'+Dependency.PackageName+'" in '+dbgs(PkgLink.Origin)+' links: "'+PkgLink.GetEffectiveFilename+'" ...']); 950 //debugln(['TLazPackageGraph.OpenDependencyWithPackageLink AFilename=',AFilename,' ',PkgLink.Origin=ploGlobal]); 951        if not FileExistsUTF8(AFilename) then begin ***Issue is here: FileExistsUTF8() returns true for a directory on Linux, (but false on windows) and the preceding GetEffectiveFilename just returns a directory Colin From aaa5500 at ya.ru Sat Nov 3 19:57:13 2018 From: aaa5500 at ya.ru (AlexeyT) Date: Sat, 3 Nov 2018 21:57:13 +0300 Subject: [Lazarus] IDE About: layout fix Message-ID: patch adds BorderSpacing.Around=6 for Memo of IDE About dialog. -- Regards, Alexey -------------- next part -------------- A non-text attachment was scrubbed... Name: ab.diff Type: text/x-patch Size: 414 bytes Desc: not available URL: From bo.berglund at gmail.com Sun Nov 4 23:19:36 2018 From: bo.berglund at gmail.com (Bo Berglund) Date: Sun, 04 Nov 2018 23:19:36 +0100 Subject: [Lazarus] Lazarus 1.8.5 IDE behaviour difference Win-Linux Message-ID: I don't kow if it is designed to be like this or else if there is a specific condition in my setup.... FPC 3.0.4 checked out from svn and built, Lazarus 1.8.5 (fixes_1_8 branch checked out via svn and built using make bigide), Ubuntu 18.04 LTS x64 with Xfce desktop in VMWare Workstation 12PRO virtual machine. When I start Lazarus the main window (on top) covers only about 75 % of the screen width. If I click the maximize button nothing happens. Only way I have found to make Lazarus cover the whole screen width is to use the mouse and grab and pull the right hand edge to the screen edge. In Windows I have a Lazarus 1.8 x64 installed from a binary release. In Windows7 when I click the maximize button the top window widens to cover the whole screen width and the button changes to the restore shape (two squares behind each other). When I click this the main window goes back to the previous size as expected. Is this behaviour only available on Windows or do I have some kind of problem in my Linux installation? -- Bo Berglund Developer in Sweden From bartjunk64 at gmail.com Sun Nov 4 23:25:19 2018 From: bartjunk64 at gmail.com (Bart) Date: Sun, 4 Nov 2018 23:25:19 +0100 Subject: [Lazarus] Lazarus 1.8.5 IDE behaviour difference Win-Linux In-Reply-To: References: Message-ID: On Sun, Nov 4, 2018 at 11:19 PM Bo Berglund via Lazarus wrote: > Is this behaviour only available on Windows or do I have some kind of > problem in my Linux installation? I have Linux Mint 18.2 64-bit in VirtualBox VM with KDE as WM (Win10 as host). When I click the maximize button of the main IDE window the window centers itself vertically on my desktop. It's unusable. Like you I manually drag the main IDE window to bee the full screen size. -- Bart From fluisgirardi at gmail.com Mon Nov 5 01:49:44 2018 From: fluisgirardi at gmail.com (Fabio Luis Girardi) Date: Sun, 4 Nov 2018 22:49:44 -0200 Subject: [Lazarus] Lazarus 1.8.5 IDE behaviour difference Win-Linux In-Reply-To: References: Message-ID: I have used laz 1.8.5 in last months and never see this issue. I have it installed in 3 PC, now running Linux mint 19 (previous are Linux mint 17.3). Em dom, 4 de nov de 2018 20:26, Bart via Lazarus < lazarus at lists.lazarus-ide.org escreveu: > On Sun, Nov 4, 2018 at 11:19 PM Bo Berglund via Lazarus > wrote: > > > Is this behaviour only available on Windows or do I have some kind of > > problem in my Linux installation? > > I have Linux Mint 18.2 64-bit in VirtualBox VM with KDE as WM (Win10 as > host). > When I click the maximize button of the main IDE window the window > centers itself vertically on my desktop. > It's unusable. > Like you I manually drag the main IDE window to bee the full screen size. > > -- > Bart > -- > _______________________________________________ > Lazarus mailing list > Lazarus at lists.lazarus-ide.org > https://lists.lazarus-ide.org/listinfo/lazarus > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bo.berglund at gmail.com Mon Nov 5 08:13:07 2018 From: bo.berglund at gmail.com (Bo Berglund) Date: Mon, 05 Nov 2018 08:13:07 +0100 Subject: [Lazarus] Lazarus 1.8.5 IDE behaviour difference Win-Linux References: Message-ID: <35rvtd9040ro6ar8frsd693t82fjipjsga@4ax.com> On Sun, 4 Nov 2018 22:49:44 -0200, Fabio Luis Girardi via Lazarus wrote: >I have used laz 1.8.5 in last months and never see this issue. I have it >installed in 3 PC, now running Linux mint 19 (previous are Linux mint 17.3). Could it be a Linux distribution issue or the choice of desktop? I can log into te regular Ubuntu desktop too, but will Lazarus then be workable? After all it was installed from the Xfce desktop so I could get a menu to put Lazarus on... I have no idea how Ubuntu 18 works concerning starting applications like Lazarus since they removed the application menu. Seems mostly unusable to me, hence my switch to Xfce. Maybe Mint is a better choice? -- Bo Berglund Developer in Sweden From nc-gaertnma at netcologne.de Mon Nov 5 11:28:58 2018 From: nc-gaertnma at netcologne.de (Mattias Gaertner) Date: Mon, 5 Nov 2018 11:28:58 +0100 Subject: [Lazarus] Lazarus Release Candidate 2 of 2.0 In-Reply-To: References: <20181101084626.39151b2e@limapholos.matflo.wg> Message-ID: <20181105112858.64242d08@limapholos.matflo.wg> On Sat, 3 Nov 2018 13:37:20 +0000 C Western via Lazarus wrote: > On 01/11/2018 07:46, Mattias Gaertner via Lazarus wrote: > > The Lazarus team is glad to announce the second release candidate of > > Lazarus 2.0. > > > I am still seeing the error on loading a (specific) package with > missing dependencies, but I have been able to do some debugging to > track down the error. It is clear I should have specified the > platform in my original message, as I think the error will not > manifest on windows. I think the error is in > packager/packagesystem.pas: > > 933    function TLazPackageGraph.OpenDependencyWithPackageLink( > > 934      Dependency: TPkgDependency; PkgLink: TPackageLink; > ShowAbort: boolean > > 935      ): TModalResult; > 942    begin > 943      NewPackage:=nil; > 944      XMLConfig:=nil; > 945      BeginUpdate(false); > 946      try > 947        AFilename:=PkgLink.GetEffectiveFilename; > 948        if pvPkgSearch in Verbosity then > 949          debugln(['Info: (lazarus) Open dependency: trying > "'+Dependency.PackageName+'" in '+dbgs(PkgLink.Origin)+' links: > "'+PkgLink.GetEffectiveFilename+'" ...']); > 950 //debugln(['TLazPackageGraph.OpenDependencyWithPackageLink > AFilename=',AFilename,' ',PkgLink.Origin=ploGlobal]); > 951        if not FileExistsUTF8(AFilename) then begin > > ***Issue is here: FileExistsUTF8() returns true for a directory on > Linux, (but false on windows) and the preceding GetEffectiveFilename > just returns a directory Thanks for debugging! I added a directoryexists check and fixed GetEffectiveFilename to not expand an empty filename. Mattias From bo.berglund at gmail.com Mon Nov 5 13:20:47 2018 From: bo.berglund at gmail.com (Bo Berglund) Date: Mon, 05 Nov 2018 13:20:47 +0100 Subject: [Lazarus] Lazarus 1.8.5 IDE behaviour difference Win-Linux References: Message-ID: <7300udplgbtjrqp4hnl7o9dun7vjgie6mo@4ax.com> On Sun, 4 Nov 2018 23:25:19 +0100, Bart via Lazarus wrote: >On Sun, Nov 4, 2018 at 11:19 PM Bo Berglund via Lazarus > wrote: > >> Is this behaviour only available on Windows or do I have some kind of >> problem in my Linux installation? > >I have Linux Mint 18.2 64-bit in VirtualBox VM with KDE as WM (Win10 as host). >When I click the maximize button of the main IDE window the window >centers itself vertically on my desktop. >It's unusable. >Like you I manually drag the main IDE window to bee the full screen size. I logged out of Xfce and logged back in to the Ubuntu standard desktop to check behaviour... Turns out that clicking the maximize button in Lazarus makes the main window cover the whole screen! I.e. it expands both sideways and down to cover *everything* with a gray panel! Seriously flawed in my mind! And completely unusable... And this is using the fixes_1_8 branch, which should hold the very latest stable fixes for 1.8. Lazarus help/about says: Version #: 1.8.5 Date: 2018-11-04 FPC version: 3.0.4 SVN Revision: 59447 (is this Lazarus or FPC?) x86_64-linux-gtk2 I am now going to get myself a Linux Mint 19 vm instead of Ubuntu... -- Bo Berglund Developer in Sweden From bo.berglund at gmail.com Mon Nov 5 14:08:35 2018 From: bo.berglund at gmail.com (Bo Berglund) Date: Mon, 05 Nov 2018 14:08:35 +0100 Subject: [Lazarus] Lazarus 1.8.5 IDE behaviour difference Win-Linux References: Message-ID: <0vf0ud5d82bn6jamvabvsaiv661rlm4t6t@4ax.com> On Sun, 4 Nov 2018 22:49:44 -0200, Fabio Luis Girardi via Lazarus wrote: >I have used laz 1.8.5 in last months and never see this issue. I have it >installed in 3 PC, now running Linux mint 19 (previous are Linux mint 17.3). I have just created a new Linux Mint 19 MATE virtual machine and installed FPC/Lazarus from sources in this. But like Bart I get the same problem when maximizing the main (top) window in Lazarus. It makes it fill the full screen rather than aligning with the top of the screen. So there is something else going on here. What desktop are you using? Cinnamon, MATE or Xfce? And did you arrive here by doing a dist-upgrade rather than a new install? -- Bo Berglund Developer in Sweden From bo.berglund at gmail.com Wed Nov 7 11:51:36 2018 From: bo.berglund at gmail.com (Bo Berglund) Date: Wed, 07 Nov 2018 11:51:36 +0100 Subject: [Lazarus] How to build FPC/Lazarus from sources on Windows? Message-ID: I am used to installing FPC/Lazarus on Linux machines from sources via svn. I have created a script that does most of the necessary stuff for this. Now I want to do the same on Windows7, but I am not really sure how. When I google I get old instructions from the Lazarus 0.9 times, so these are not especially useful. Just one item: make This is a necessary item to be able to build both FPC and Lazarus, yet on my machine the only make utility I find are these: where make C:\Programs\CodeGear\RAD Studio\6.0\bin\make.exe C:\Programs\Embarcadero\RAD Studio\12.0\bin\make.exe C:\Programs\Borland\BDS\4.0\Bin\make.exe C:\Programs\CodeGear\RAD Studio\5.0\bin\make.exe C:\Programs\Borland\Delphi7\Bin\make.exe As you can see there are no less than 5 different make utilities all coming from various installations of Delphi/RAD Studio. Are these OK to use or do I need to get (how?) some other make utility? Maybe a GNU version??? Is there an up-to-date page describing the exact procedure to build FPC and Lazarus from sources retrieved via SVN on Windows? I do have several older versions of Lazarus/fpc installed already (1.6, 1.8, 1.8.4 32 bit) but none seems to put fpc.exe on path. The fpc version for the 1.8.x lazarus is 3.0.4 bundeled with their respective and 1.6 uses fpc 3.0.0. I want to move forward with this and not rely on some binary package if possible. -- Bo Berglund Developer in Sweden From bo.berglund at gmail.com Wed Nov 7 12:23:29 2018 From: bo.berglund at gmail.com (Bo Berglund) Date: Wed, 07 Nov 2018 12:23:29 +0100 Subject: [Lazarus] How to build FPC/Lazarus from sources on Windows? References: Message-ID: On Wed, 07 Nov 2018 11:51:36 +0100, Bo Berglund via lazarus wrote: >Is there an up-to-date page describing the exact procedure to build >FPC and Lazarus from sources retrieved via SVN on Windows? > After posting I found this page: http://wiki.lazarus.freepascal.org/Installing_Lazarus#Compiling.2Finstalling_FPC_and_Lazarus_from_Sources_of_SVN_.28Win32.29 Maybe this is the definite instruction? I will have a look and see if it works out like I need... -- Bo Berglund Developer in Sweden From bo.berglund at gmail.com Wed Nov 7 14:22:24 2018 From: bo.berglund at gmail.com (Bo Berglund) Date: Wed, 07 Nov 2018 14:22:24 +0100 Subject: [Lazarus] How to build FPC/Lazarus from sources on Windows? References: Message-ID: On Wed, 07 Nov 2018 12:23:29 +0100, Bo Berglund via lazarus wrote: >On Wed, 07 Nov 2018 11:51:36 +0100, Bo Berglund via lazarus > wrote: > >>Is there an up-to-date page describing the exact procedure to build >>FPC and Lazarus from sources retrieved via SVN on Windows? >> >After posting I found this page: > >http://wiki.lazarus.freepascal.org/Installing_Lazarus#Compiling.2Finstalling_FPC_and_Lazarus_from_Sources_of_SVN_.28Win32.29 > >Maybe this is the definite instruction? >I will have a look and see if it works out like I need... > A question: This page deals with 32 bit fpc/lazarus at least on Windows... If I want to build the 64 bit version, where should I then put the 64 bit binutils? The suggested path c:\freepascal\binutils\i386-win32\ seems incorrect. Could I set it to c:\freepascal\binutils\x86_64-win64\ ? Or does it not matter? I really would like to have both 32 and 64 bit available. -- Bo Berglund Developer in Sweden From jmlandmesser at gmx.de Wed Nov 7 21:51:45 2018 From: jmlandmesser at gmx.de (John Landmesser) Date: Wed, 7 Nov 2018 21:51:45 +0100 Subject: [Lazarus] How to build FPC/Lazarus from sources on Windows? In-Reply-To: References: Message-ID: have a look at: http://wiki.freepascal.org/fpcupdeluxe that should be sufficient?!! Am 07.11.18 um 14:22 schrieb Bo Berglund via lazarus: > On Wed, 07 Nov 2018 12:23:29 +0100, Bo Berglund via lazarus > wrote: > >> On Wed, 07 Nov 2018 11:51:36 +0100, Bo Berglund via lazarus >> wrote: >> >>> Is there an up-to-date page describing the exact procedure to build >>> FPC and Lazarus from sources retrieved via SVN on Windows? >>> >> After posting I found this page: >> >> http://wiki.lazarus.freepascal.org/Installing_Lazarus#Compiling.2Finstalling_FPC_and_Lazarus_from_Sources_of_SVN_.28Win32.29 >> >> Maybe this is the definite instruction? >> I will have a look and see if it works out like I need... >> > A question: > This page deals with 32 bit fpc/lazarus at least on Windows... > If I want to build the 64 bit version, where should I then put the 64 > bit binutils? > The suggested path c:\freepascal\binutils\i386-win32\ seems incorrect. > > Could I set it to c:\freepascal\binutils\x86_64-win64\ ? > Or does it not matter? I really would like to have both 32 and 64 bit > available. > > From leledumbo_cool at yahoo.co.id Thu Nov 8 02:39:59 2018 From: leledumbo_cool at yahoo.co.id (leledumbo) Date: Wed, 7 Nov 2018 18:39:59 -0700 (MST) Subject: [Lazarus] How to build FPC/Lazarus from sources on Windows? In-Reply-To: References: Message-ID: <1541641199639-0.post@n3.nabble.com> > If I want to build the 64 bit version, where should I then put the 64 bit binutils? Wherever -FD in your fpc.cfg points to (remember, fpc.cfg supports conditionals). > The suggested path c:\freepascal\binutils\i386-win32\ seems incorrect. Why not? The binutils itself could still be 32-bit while generating 64-bit binaries. Native 64-bit shouldn't be there, of course. -- Sent from: http://free-pascal-lazarus.989080.n3.nabble.com/ From bo.berglund at gmail.com Thu Nov 8 13:23:28 2018 From: bo.berglund at gmail.com (Bo Berglund) Date: Thu, 08 Nov 2018 13:23:28 +0100 Subject: [Lazarus] How to build FPC/Lazarus from sources on Windows? References: <1541641199639-0.post@n3.nabble.com> Message-ID: On Wed, 7 Nov 2018 18:39:59 -0700 (MST), leledumbo via lazarus wrote: >> If I want to build the 64 bit version, where should I then put the 64 bit >binutils? > >Wherever -FD in your fpc.cfg points to (remember, fpc.cfg supports >conditionals). > >> The suggested path c:\freepascal\binutils\i386-win32\ seems incorrect. > >Why not? The binutils itself could still be 32-bit while generating 64-bit >binaries. Native 64-bit shouldn't be there, of course. So in fact I don't really need the 64 bit versions of the binutil files? I looked further down on the page I found and noted this regarding creation of the bat file used to build fpc: For crosscompiler to x86_64 add the following after the first make: make all OS_TARGET=win64 CPU_TARGET=x86_64 INSTALL_PREFIX=%myFPC% PP=%mybinutils%\ppc386.exe DATA2INC=%myFPC%\utils\data2inc.exe make crossinstall OS_TARGET=win64 CPU_TARGET=x86_64 INSTALL_PREFIX=%myFPC% PP=%mybinutils%\ppc386.exe DATA2INC=%myFPC%\utils\data2inc.exe It rather looks like I don't need two different Lazarus installations in order to build for both 32 and 64 bit windows, right? In that case should I not focus on the 64 bit version and have 32 bit as a crosscompile target? I.e. Use Lazarus 64 bit to sometimes create a 32 bit program through cross-compile. Now I am unsure of what kind of Lazaruses I really do have (4 versions at the moment). Is there a simple way to check if lazaus itself is 32 or 64 bit? For Lazarus the bat file looks like this: set myroot=c:\freepascal set myFPC=%myroot%\fpc\3.0.4 set mybinutils=%myroot%\binutils set PATH=%mybinutils%\i386-win32;%myFPC%\bin\i386-win32;%PATH% cd %myroot%\laz make clean all OPT="-glw2 -Xg" Will it build a 64 or 32 bit version of Lazarus? Looks like it uses 32 bit paths... -- Bo Berglund Developer in Sweden From md at delfire.net Thu Nov 8 13:29:15 2018 From: md at delfire.net (Marcos Douglas B. Santos) Date: Thu, 8 Nov 2018 10:29:15 -0200 Subject: [Lazarus] How to build FPC/Lazarus from sources on Windows? In-Reply-To: References: Message-ID: On Wed, Nov 7, 2018 at 9:23 AM Bo Berglund via lazarus wrote: > > On Wed, 07 Nov 2018 11:51:36 +0100, Bo Berglund via lazarus > wrote: > > >Is there an up-to-date page describing the exact procedure to build > >FPC and Lazarus from sources retrieved via SVN on Windows? > > > After posting I found this page: > > http://wiki.lazarus.freepascal.org/Installing_Lazarus#Compiling.2Finstalling_FPC_and_Lazarus_from_Sources_of_SVN_.28Win32.29 > > Maybe this is the definite instruction? > I will have a look and see if it works out like I need... I made this page - then others have updated too. I've been using this script (my own, updated, you can get here[1]) for many years, however using fpcupdeluxe is much simpler. [1] https://github.com/mdbs99/fp-scripts regards, Marcos Douglas From md at delfire.net Thu Nov 8 13:33:45 2018 From: md at delfire.net (Marcos Douglas B. Santos) Date: Thu, 8 Nov 2018 10:33:45 -0200 Subject: [Lazarus] How to build FPC/Lazarus from sources on Windows? In-Reply-To: References: <1541641199639-0.post@n3.nabble.com> Message-ID: On Thu, Nov 8, 2018 at 10:23 AM Bo Berglund via lazarus wrote: > > On Wed, 7 Nov 2018 18:39:59 -0700 (MST), leledumbo via lazarus > wrote: > > >> If I want to build the 64 bit version, where should I then put the 64 bit > >binutils? > > > >Wherever -FD in your fpc.cfg points to (remember, fpc.cfg supports > >conditionals). > > > >> The suggested path c:\freepascal\binutils\i386-win32\ seems incorrect. > > > >Why not? The binutils itself could still be 32-bit while generating 64-bit > >binaries. Native 64-bit shouldn't be there, of course. > > So in fact I don't really need the 64 bit versions of the binutil > files? > > I looked further down on the page I found and noted this regarding > creation of the bat file used to build fpc: > > For crosscompiler to x86_64 add the following after the first make: > > make all OS_TARGET=win64 CPU_TARGET=x86_64 INSTALL_PREFIX=%myFPC% > PP=%mybinutils%\ppc386.exe DATA2INC=%myFPC%\utils\data2inc.exe > make crossinstall OS_TARGET=win64 CPU_TARGET=x86_64 > INSTALL_PREFIX=%myFPC% PP=%mybinutils%\ppc386.exe > DATA2INC=%myFPC%\utils\data2inc.exe > > It rather looks like I don't need two different Lazarus installations > in order to build for both 32 and 64 bit windows, right? > In that case should I not focus on the 64 bit version and have 32 bit > as a crosscompile target? > > I.e. Use Lazarus 64 bit to sometimes create a 32 bit program through > cross-compile. > > Now I am unsure of what kind of Lazaruses I really do have (4 versions > at the moment). Is there a simple way to check if lazaus itself is 32 > or 64 bit? > > For Lazarus the bat file looks like this: > > set myroot=c:\freepascal > set myFPC=%myroot%\fpc\3.0.4 > set mybinutils=%myroot%\binutils > set PATH=%mybinutils%\i386-win32;%myFPC%\bin\i386-win32;%PATH% > cd %myroot%\laz > make clean all OPT="-glw2 -Xg" > > Will it build a 64 or 32 bit version of Lazarus? > Looks like it uses 32 bit paths... See here - https://github.com/mdbs99/fp-scripts/blob/master/fpc-make.bat#L54-L58 At least for Windows, you might install i386-win32 version then, if you want, compile a x86_64 version as explained on script above. But, again, try fpcupdeluxe... "there is not life without it" :) regards, Marcos Douglas From coppolastudio at gmail.com Thu Nov 8 15:51:59 2018 From: coppolastudio at gmail.com (coppolastudio) Date: Thu, 08 Nov 2018 15:51:59 +0100 Subject: [Lazarus] How to build FPC/Lazarus from sources on Windows? References: Message-ID: <7qbl7mq99rko3af6ue7ilh7d.1541688720031@email.kingsoft.com> An HTML attachment was scrubbed... URL: From bo.berglund at gmail.com Thu Nov 8 18:07:06 2018 From: bo.berglund at gmail.com (Bo Berglund) Date: Thu, 08 Nov 2018 18:07:06 +0100 Subject: [Lazarus] How to build FPC/Lazarus from sources on Windows? References: Message-ID: On Wed, 7 Nov 2018 21:51:45 +0100, John Landmesser via lazarus wrote: >have a look at: > >http://wiki.freepascal.org/fpcupdeluxe > >that should be sufficient?!! > Looks interesting! But I have a request: I tried to set it up for installing fpc fixes3.2 x86_64 on windows and also wanted to set the crosscompiler installation. Plus selecting the lazarus version. But then when I clicked the Install cross-compiler button to select which crosscompiler to choose, it started a pretty long process which clearly was not wanted and I saw no way to stop it! It failed since it could not read some file that was supposed to be there I guess. Later I found a button way down to the right named Halt! Is that what is supposed to be used for such mistakes as I did? Please add a confirmation box *before* operations are started so mistakes like this can be avoided. Regarding crosscompilers: How can I set up those when there is no selector for *which* crosscompiler I want to also install? The CPU selector seems to be just a single selector option box. Anyway I corrected what I did wrong and set it in motion. Took a while and then it stopped with: C:\fpc\lazarus\components\lazutils\utf8process.pp(362,69) Error: (3285) Expected another 2 array elements utf8process.pp(695) Fatal: (10026) There were 1 errors compiling module, stopping Fatal: (1018) Compilation aborted Error: C:\fpc\fpc\bin\x86_64-win64\ppcx64.exe returned an error exitcode C:\fpc\fpcbootstrap\make.exe: *** [lazutils] Error 2 fpcupdeluxe: ERROR: LazarusNativeInstaller (BuildModuleCustom: Lazbuild): make.exe returned error code #2 ERROR: Fpcupdeluxe fatal error ! So what is the deal now? -- Bo Berglund Developer in Sweden From alfred at consulab.nl Fri Nov 9 09:24:32 2018 From: alfred at consulab.nl (Alfred) Date: Fri, 09 Nov 2018 08:24:32 +0000 Subject: [Lazarus] How to build FPC/Lazarus from sources on Windows? In-Reply-To: References: Message-ID: Fpcupdeluxe tries to install an isolated version of FPC and Lazarus. And can help you in installing cross-compilers for this isolated version. Sequence: First, install a suitable FPC (and Lazarus) version with fpcupdeluxe in a directory of choice. (in you case FPC fixes 3.2 (and Lazarus fixes 2.0 or trunk)) After this process has finished, you can install a cross-compiler. Choose a CPU and OS and click install cross-compiler. In most cases, this process will fail due to missing libs and bins. Allow fpcupdeluxe to download the libs and bins and continue with the process. The second run should end with a successful build of the cross-compiler. Keep in mind: many things can go wrong during the process. The output should give you more clues in case of errors. If so, you can report them in the forum. ------ Origineel bericht ------ Van: "Bo Berglund via lazarus" Aan: lazarus at lists.lazarus.freepascal.org CC: "Bo Berglund" Verzonden: 8-11-2018 18:07:06 Onderwerp: Re: [Lazarus] How to build FPC/Lazarus from sources on Windows? >On Wed, 7 Nov 2018 21:51:45 +0100, John Landmesser via lazarus > wrote: > >>have a look at: >> >>http://wiki.freepascal.org/fpcupdeluxe >> >>that should be sufficient?!! >> > >Looks interesting! >But I have a request: >I tried to set it up for installing fpc fixes3.2 x86_64 on windows and >also wanted to set the crosscompiler installation. Plus selecting the >lazarus version. > >But then when I clicked the Install cross-compiler button to select >which crosscompiler to choose, it started a pretty long process which >clearly was not wanted and I saw no way to stop it! >It failed since it could not read some file that was supposed to be >there I guess. Later I found a button way down to the right named >Halt! Is that what is supposed to be used for such mistakes as I did? > >Please add a confirmation box *before* operations are started so >mistakes like this can be avoided. > >Regarding crosscompilers: >How can I set up those when there is no selector for *which* >crosscompiler I want to also install? The CPU selector seems to be >just a single selector option box. > > >Anyway I corrected what I did wrong and set it in motion. >Took a while and then it stopped with: > >C:\fpc\lazarus\components\lazutils\utf8process.pp(362,69) Error: >(3285) Expected another 2 array elements >utf8process.pp(695) Fatal: (10026) There were 1 errors compiling >module, stopping >Fatal: (1018) Compilation aborted >Error: C:\fpc\fpc\bin\x86_64-win64\ppcx64.exe returned an error >exitcode >C:\fpc\fpcbootstrap\make.exe: *** [lazutils] Error 2 >fpcupdeluxe: ERROR: LazarusNativeInstaller (BuildModuleCustom: >Lazbuild): make.exe returned error code #2 > > >ERROR: Fpcupdeluxe fatal error ! > >So what is the deal now? > >-- >Bo Berglund >Developer in Sweden > >-- >_______________________________________________ >lazarus mailing list >lazarus at lists.lazarus-ide.org >https://lists.lazarus-ide.org/listinfo/lazarus From dezlov at gmail.com Tue Nov 13 08:49:42 2018 From: dezlov at gmail.com (Denis Kozlov) Date: Tue, 13 Nov 2018 07:49:42 +0000 Subject: [Lazarus] Long paths manifest Message-ID: <74bc3c19-d97e-b1e7-db4c-cdcbe8047666@gmail.com> Hello, Windows API is capable of working with extended-length path for a maximum total path length of 32,767 characters, thus, overcoming the infamous 260 characters path limitation (a.k.a. MAX_PATH). To specify an extended-length path, use the "\\?\" prefix. For example, "\\?\C:\Very\Long\Path". According to Windows Docs, one can enable the new long path behavior per app via the manifest: -----------------------------     true     ----------------------------- Has anyone had any experience with embedding such manifest? What would be the best way to add such a manifest to an application, currently? Perhaps this could be added as an option in Lazarus IDE, similarly to the option for enabling themes support. For the reference: Windows Docs - Naming Files, Paths, and Namespaces - Maximum Path Length Limitation https://docs.microsoft.com/en-us/windows/desktop/FileIO/naming-a-file#maximum-path-length-limitation Regards, Denis From aaa5500 at ya.ru Tue Nov 13 09:26:05 2018 From: aaa5500 at ya.ru (AlexeyT) Date: Tue, 13 Nov 2018 11:26:05 +0300 Subject: [Lazarus] Long paths manifest In-Reply-To: <74bc3c19-d97e-b1e7-db4c-cdcbe8047666@gmail.com> References: <74bc3c19-d97e-b1e7-db4c-cdcbe8047666@gmail.com> Message-ID: --File I/O functions in the Windows API convert "/" to "\" as part of converting the name to an NT-style name, except when using the "\\?\" prefix as detailed in the following sections. So apps may have new bugs from this prefix. when app uses / shashes (fn := dir + '/' + name) by mistake. Alex From vojtech.cihak at atlas.cz Mon Nov 19 21:09:45 2018 From: vojtech.cihak at atlas.cz (=?utf-8?q?Vojt=C4=9Bch_=C4=8Cih=C3=A1k?=) Date: Mon, 19 Nov 2018 21:09:45 +0100 Subject: [Lazarus] =?utf-8?q?Text_in_console_in/output_mirrored?= Message-ID: <20181119210945.FD858610@atlas.cz> Hi,   it's funny, text is mirrored.   DebugLn('May the Force be with you.');   writes .uoy htiw eb ecroF eht yaM   Lazarus 2.1.0 r59610 FPC 3.3.1 x86_64-linux-qt   V. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dezlov at gmail.com Mon Nov 19 23:17:12 2018 From: dezlov at gmail.com (Denis Kozlov) Date: Mon, 19 Nov 2018 22:17:12 +0000 Subject: [Lazarus] Long paths manifest In-Reply-To: <74bc3c19-d97e-b1e7-db4c-cdcbe8047666@gmail.com> References: <74bc3c19-d97e-b1e7-db4c-cdcbe8047666@gmail.com> Message-ID: Any thoughts on integrating the long paths manifest into Lazarus as a project option? On 13/11/2018 07:49, Denis Kozlov wrote: > Hello, > > Windows API is capable of working with extended-length path for a > maximum total path length of 32,767 characters, thus, overcoming the > infamous 260 characters path limitation (a.k.a. MAX_PATH). To specify > an extended-length path, use the "\\?\" prefix. For example, > "\\?\C:\Very\Long\Path". > > According to Windows Docs, one can enable the new long path behavior > per app via the manifest: > ----------------------------- > >     xmlns:ws2="http://schemas.microsoft.com/SMI/2016/WindowsSettings"> > true >     > > ----------------------------- > > Has anyone had any experience with embedding such manifest? What would > be the best way to add such a manifest to an application, currently? > > Perhaps this could be added as an option in Lazarus IDE, similarly to > the option for enabling themes support. > > For the reference: > Windows Docs - Naming Files, Paths, and Namespaces - Maximum Path > Length Limitation > https://docs.microsoft.com/en-us/windows/desktop/FileIO/naming-a-file#maximum-path-length-limitation > > > Regards, > Denis From aaa5500 at ya.ru Tue Nov 20 00:46:25 2018 From: aaa5500 at ya.ru (AlexeyT) Date: Tue, 20 Nov 2018 02:46:25 +0300 Subject: [Lazarus] Long paths manifest In-Reply-To: References: <74bc3c19-d97e-b1e7-db4c-cdcbe8047666@gmail.com> Message-ID: <97fd58c2-e220-693f-b343-3e4b8d0d5477@ya.ru> On 20.11.2018 1:17, Denis Kozlov via lazarus wrote: > Any thoughts on integrating I'm making the patch. I dont know on which XML level to insert new XML part - inside or out of it in the root?     true     -- Regards, Alexey From aaa5500 at ya.ru Tue Nov 20 01:14:42 2018 From: aaa5500 at ya.ru (AlexeyT) Date: Tue, 20 Nov 2018 03:14:42 +0300 Subject: [Lazarus] Long paths manifest In-Reply-To: References: <74bc3c19-d97e-b1e7-db4c-cdcbe8047666@gmail.com> Message-ID: https://bugs.freepascal.org/view.php?id=34573 my attempt. I'm not sure about correct place of XML option. I did it like this page shows: https://gist.github.com/riverar/196d5aa6bb53bbdfb50beb323d0709df . So pls check it in work. AT From aaa5500 at ya.ru Tue Nov 20 04:20:24 2018 From: aaa5500 at ya.ru (AlexeyT) Date: Tue, 20 Nov 2018 06:20:24 +0300 Subject: [Lazarus] IDE Project Options - icon needed Message-ID: Button "Load default" in Icon group - needs new icon, which is used for "set default" buttons in IDE. it is brown curved arrow. -- Regards, Alexey From dec12 at avidsoft.com.hk Tue Nov 20 11:37:55 2018 From: dec12 at avidsoft.com.hk (Dennis) Date: Tue, 20 Nov 2018 18:37:55 +0800 Subject: [Lazarus] what can we do to get a better debugger Message-ID: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> FPC and Lazarus are great but the GDB is inadequate. Many times in my development, GDB failed or crashed, especially when I am debugging multi thread programs. Shall we start a fund raising event to raise fund for a new and better debugger for FPC + Lazarus? (provided there are talents out there who would do implement it). Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From eduardo.tognazza at bluewin.ch Tue Nov 20 11:48:33 2018 From: eduardo.tognazza at bluewin.ch (eduardo.tognazza) Date: Tue, 20 Nov 2018 11:48:33 +0100 Subject: [Lazarus] what can we do to get a better debugger In-Reply-To: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> References: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> Message-ID: my donation is safe for that. > FPC and Lazarus are great but the GDB is inadequate. > Many times in my development, GDB failed or crashed, especially when I > am debugging multi thread programs. > > Shall we start a fund raising event to raise fund for a new and better > debugger for FPC + Lazarus? (provided there are talents out there who > would do implement it). > > Dennis > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lazarus at mfriebe.de Tue Nov 20 12:19:40 2018 From: lazarus at mfriebe.de (Martin Frb) Date: Tue, 20 Nov 2018 12:19:40 +0100 Subject: [Lazarus] what can we do to get a better debugger In-Reply-To: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> References: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> Message-ID: <91f961f8-c5e6-1dff-bfa0-9dc1f1cfc08d@mfriebe.de> On 20/11/2018 11:37, Dennis via lazarus wrote: > FPC and Lazarus are great but the GDB is inadequate. > Many times in my development, GDB failed or crashed, especially when I > am debugging multi thread programs. > > Shall we start a fund raising event to raise fund for a new and better > debugger for FPC + Lazarus? (provided there are talents out there who > would do implement it). That work is already in process (though very slowly / work has started/stopped plenty of times over the past many years). It is called FpDebug. Donations are still welcome. Under Windows and Linux you can install the package LazDebuggerFp. (You can do on Mac too, but then you need to codesign the entire IDE). Best use Lazarus trunk (it is already ahead of fixes 2.0 branch, but by very little only) Support for threaded apps in fpdebug is not yet there. Under Linux only the main thread is debugged. Windows has bare minimum  (and untested) support for dealing with threads. About using gdb. - If on windows, test the alternative gdb downloads from our sourceforge site. (Newer is not always better / but there is no generally best version, depends on many factors). - Do not use dwarf3, this increases the risk of gdb crashes ("dwarf2 with sets" is recommended) - On win64, there are issues with single stepping. Potential workaround: compile the project (and all packages that have debug info) with -Xe -al (external linker and assemble) => that is slow, but may help - Always ensure that all packages have the same type of debug info. If you compile the project with "dwarf with sets", then any package (unless it has no debug info) should also use "dwarf with sets" ("dwarf2"  (aka "dwarf"/-gw in the IDE) and "dwarf with sets" are compatible too). You can use "additions and overrides" to ensure this. - Absolutely stay away from smart linking (for debugging). You can compile the units "smart linkable". But do not actually "smart link" the exe - Not related to crashes, but stay with "NO optimization" -O- - (fixes 2.0) On the debugger option (property grid): check and maybe reduce the various memory limits. If crashes happen while examining values try installing the package LazDebuggerFpGdbmi, and set the debugger type to "gdb (with fpdebug)". All the above still applies. Though yes, in the end, gdb may still crash. Depends on lots of stuff in your app. For Mac, we have an LLDB based debugger now. It works on other platform too (if lldb is available and stable). But it is less feature rich. Also check http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips -------------- next part -------------- An HTML attachment was scrubbed... URL: From Special at Joepgen.com Tue Nov 20 13:29:48 2018 From: Special at Joepgen.com (Joe) Date: Tue, 20 Nov 2018 13:29:48 +0100 Subject: [Lazarus] what can we do to get a better debugger In-Reply-To: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> References: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> Message-ID: <560583c5-d64a-b685-b9c8-d8e72fef87f7@Joepgen.com> Am 20.11.2018 um 11:37 schrieb Dennis via lazarus: > FPC and Lazarus are great but the GDB is inadequate. > Many times in my development, GDB failed or crashed, especially when I > am debugging multi thread programs. > > Shall we start a fund raising event to raise fund for a new and better > debugger for FPC + Lazarus? (provided there are talents out there who > would do implement it). > > Dennis > Yes, we should, I think. Joe -------------- next part -------------- An HTML attachment was scrubbed... URL: From listbox at martoks-place.de Tue Nov 20 17:19:29 2018 From: listbox at martoks-place.de (Martok) Date: Tue, 20 Nov 2018 17:19:29 +0100 Subject: [Lazarus] what can we do to get a better debugger In-Reply-To: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> References: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> Message-ID: Am 20.11.2018 um 11:37 schrieb Dennis via lazarus: > FPC and Lazarus are great but the GDB is inadequate. > Many times in my development, GDB failed or crashed, especially when I am > debugging multi thread programs. > > Shall we start a fund raising event to raise fund for a new and better debugger > for FPC + Lazarus? (provided there are talents out there who would do implement it). So much this. GDB needs to die in a fire. (nb: make sure to enable "Reset debugger after every run". That at least works around the absurd amount of memory leaks, and helps with lost breakpoints.) -- Regards, Martok Ceterum censeo b32079 esse sanandam. From vojtech.cihak at atlas.cz Tue Nov 20 17:29:12 2018 From: vojtech.cihak at atlas.cz (=?utf-8?q?Vojt=C4=9Bch_=C4=8Cih=C3=A1k?=) Date: Tue, 20 Nov 2018 17:29:12 +0100 Subject: [Lazarus] =?utf-8?q?Text_in_console_in/output_mirrored?= In-Reply-To: 0000000092b60001cae001a25081 References: 0000000092b60001cae001a25081 Message-ID: <20181120172912.0B6145E6@atlas.cz> Hi,   it's caused by 59589 (https://svn.freepascal.org/cgi-bin/viewvc.cgi/trunk/debugger/pseudoterminaldlg.pp?root=lazarus&r1=59589&r2=59588&pathrev=59589).   V. ______________________________________________________________ > Od: "Vojtěch Čihák via lazarus" > Komu: "Lazarus mailing list" > Datum: 19.11.2018 21:09 > Předmět: [Lazarus] Text in console in/output mirrored > Hi,   it's funny, text is mirrored.   DebugLn('May the Force be with you.');   writes   .uoy htiw eb ecroF eht yaM   Lazarus 2.1.0 r59610 FPC 3.3.1 x86_64-linux-qt   V. ---------- -- _______________________________________________ lazarus mailing list lazarus at lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus -------------- next part -------------- An HTML attachment was scrubbed... URL: From dec12 at avidsoft.com.hk Tue Nov 20 17:31:48 2018 From: dec12 at avidsoft.com.hk (Dennis) Date: Wed, 21 Nov 2018 00:31:48 +0800 Subject: [Lazarus] what can we do to get a better debugger In-Reply-To: References: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> Message-ID: Martok via lazarus wrote: > Am 20.11.2018 um 11:37 schrieb Dennis via lazarus: >> FPC and Lazarus are great but the GDB is inadequate. >> Many times in my development, GDB failed or crashed, especially when I am >> debugging multi thread programs. >> >> Shall we start a fund raising event to raise fund for a new and better debugger >> for FPC + Lazarus? (provided there are talents out there who would do implement it). > So much this. GDB needs to die in a fire. > > (nb: make sure to enable "Reset debugger after every run". That at least works > around the absurd amount of memory leaks, and helps with lost breakpoints.) > I cannot find this "Reset debugger after every run" option in the Lazarus options. Is it set by a command switch? How to set it? Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hkpaiedfbpapaild.png Type: image/png Size: 27584 bytes Desc: not available URL: From lazarus at mfriebe.de Tue Nov 20 17:37:21 2018 From: lazarus at mfriebe.de (Martin Frb) Date: Tue, 20 Nov 2018 17:37:21 +0100 Subject: [Lazarus] what can we do to get a better debugger In-Reply-To: References: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> Message-ID: <1779e38b-ea2d-dcc7-ff7b-b6c14697a460@mfriebe.de> On 20/11/2018 17:31, Dennis via lazarus wrote: > > > Martok via lazarus wrote: >> Am 20.11.2018 um 11:37 schrieb Dennis via lazarus: >>> FPC and Lazarus are great but the GDB is inadequate. >>> Many times in my development, GDB failed or crashed, especially when I am >>> debugging multi thread programs. >>> >>> Shall we start a fund raising event to raise fund for a new and better debugger >>> for FPC + Lazarus? (provided there are talents out there who would do implement it). >> So much this. GDB needs to die in a fire. >> >> (nb: make sure to enable "Reset debugger after every run". That at least works >> around the absurd amount of memory leaks, and helps with lost breakpoints.) >> > > I cannot find this > "Reset debugger after every run" Its an IDE global option. Menu: Tools > Options Page: Debugger > General That is also where you can set memory limits for gdb (in Lazarus 2.0) -------------- next part -------------- An HTML attachment was scrubbed... URL: From nc-gaertnma at netcologne.de Tue Nov 20 17:42:11 2018 From: nc-gaertnma at netcologne.de (Mattias Gaertner) Date: Tue, 20 Nov 2018 17:42:11 +0100 Subject: [Lazarus] Text in console in/output mirrored In-Reply-To: <20181120172912.0B6145E6@atlas.cz> References: <20181120172912.0B6145E6@atlas.cz> Message-ID: <20181120174211.08efebc7@limapholos.matflo.wg> On Tue, 20 Nov 2018 17:29:12 +0100 Vojtěch Čihák via lazarus wrote: > Hi, >   > it's caused by 59589 > (https://svn.freepascal.org/cgi-bin/viewvc.cgi/trunk/debugger/pseudoterminaldlg.pp?root=lazarus&r1=59589&r2=59588&pathrev=59589). > V. Sorry, fixed. Mattias From vojtech.cihak at atlas.cz Tue Nov 20 18:17:02 2018 From: vojtech.cihak at atlas.cz (=?utf-8?q?Vojt=C4=9Bch_=C4=8Cih=C3=A1k?=) Date: Tue, 20 Nov 2018 18:17:02 +0100 Subject: [Lazarus] =?utf-8?q?Text_in_console_in/output_mirrored?= In-Reply-To: 0000000092c70001ea7001a25057 References: <20181120172912.0B6145E6@atlas.cz> 0000000092c70001ea7001a25057 Message-ID: <20181120181702.E5675BDC@atlas.cz> Not yet OK, unfortunately. Text is not mirrored but looks like this (missing first letters of the words): Heap ump y eaptrc nit f media/homeM/v1/Projects/ECSAS/ecsas 270869 emory locks llocated 7659478/78044368 270869 emory locks reed 7659478/78044368 0 nfreed emory locks True eap ize 111808 True ree eap 111808   and when I stop app I have Range Check Error - see attachment.   Thanks, V.   ______________________________________________________________ > Od: "Mattias Gaertner via lazarus" > Komu: lazarus at lists.lazarus-ide.org > Datum: 20.11.2018 17:42 > Předmět: Re: [Lazarus] Text in console in/output mirrored > On Tue, 20 Nov 2018 17:29:12 +0100 Vojtěch Čihák via lazarus wrote: > Hi, >   > it's caused by 59589 > (https://svn.freepascal.org/cgi-bin/viewvc.cgi/trunk/debugger/pseudoterminaldlg.pp?root=lazarus&r1=59589&r2=59588&pathrev=59589 ). > V. Sorry, fixed. Mattias -- _______________________________________________ lazarus mailing list lazarus at lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pseudoterm.png Type: image/png Size: 65482 bytes Desc: pseudoterm.png URL: From nc-gaertnma at netcologne.de Tue Nov 20 22:07:07 2018 From: nc-gaertnma at netcologne.de (Mattias Gaertner) Date: Tue, 20 Nov 2018 22:07:07 +0100 Subject: [Lazarus] Text in console in/output mirrored In-Reply-To: <20181120181702.E5675BDC@atlas.cz> References: <20181120172912.0B6145E6@atlas.cz> <20181120181702.E5675BDC@atlas.cz> Message-ID: <20181120220707.33bd769d@limapholos.matflo.wg> On Tue, 20 Nov 2018 18:17:02 +0100 Vojtěch Čihák via lazarus wrote: > Not yet OK, unfortunately. Text is not mirrored but looks like this > (missing first letters of the words): > > Heap ump y eaptrc nit f media/homeM/v1/Projects/ECSAS/ecsas > 270869 emory locks llocated 7659478/78044368 > 270869 emory locks reed 7659478/78044368 > 0 nfreed emory locks > True eap ize 111808 > True ree eap 111808 >   > and when I stop app I have Range Check Error - see attachment. Second try. Fixed. Mattias From mail at michael-ring.org Tue Nov 20 22:44:22 2018 From: mail at michael-ring.org (Michael Ring) Date: Tue, 20 Nov 2018 22:44:22 +0100 Subject: [Lazarus] Switching debugger based on Project settings for embedded targets Message-ID: <30238cc9-dd5d-634f-7896-f37d1c8f4e85@michael-ring.org> Hi! Since a while I am using lazarus not only to edit/compile projects for embededded controllers, but also debugging now works very nicely. There is only one issue I see at the moment, the debugger is a global setting, afaik I cannot change the debugger configuration based on a project. The problem is that for debugging arm I will have to use arm-none-eabi-gdb, for pic32 I will have to use mips-sde-elf-gdb for debugging and both will have to use a special debugger class for interfacing with Segger JLink Debug Probe and possibly openocd in the future. Other people, that use Lazaeus for Windows/Linux/Mac Development would also need to change the global setting when switching from embedded development to native development to the default gdb debugger. What is the best way to implement this project based override, I guess I can do the coding myself as I have also created my own debugger for JLink, but I do not know how to do this debugger switching in the proper 'Lazarus' way..... Thanks in advance, Michael From vojtech.cihak at atlas.cz Tue Nov 20 22:51:14 2018 From: vojtech.cihak at atlas.cz (=?utf-8?q?Vojt=C4=9Bch_=C4=8Cih=C3=A1k?=) Date: Tue, 20 Nov 2018 22:51:14 +0100 Subject: [Lazarus] =?utf-8?q?Text_in_console_in/output_mirrored?= In-Reply-To: 0000000092c90001ee4001a2505a References: <20181120172912.0B6145E6@atlas.cz>, <20181120181702.E5675BDC@atlas.cz> 0000000092c90001ee4001a2505a Message-ID: <20181120225114.5FCF9A18@atlas.cz> Thankś, r.59612 is OK.   V. ______________________________________________________________ > Od: "Mattias Gaertner via lazarus" > Komu: lazarus at lists.lazarus-ide.org > Datum: 20.11.2018 22:07 > Předmět: Re: [Lazarus] Text in console in/output mirrored > On Tue, 20 Nov 2018 18:17:02 +0100 Vojtěch Čihák via lazarus wrote: Second try. Fixed. Mattias -- _______________________________________________ lazarus mailing list lazarus at lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus -------------- next part -------------- An HTML attachment was scrubbed... URL: From lazarus at mfriebe.de Wed Nov 21 00:07:58 2018 From: lazarus at mfriebe.de (Martin Frb) Date: Wed, 21 Nov 2018 00:07:58 +0100 Subject: [Lazarus] Switching debugger based on Project settings for embedded targets In-Reply-To: <30238cc9-dd5d-634f-7896-f37d1c8f4e85@michael-ring.org> References: <30238cc9-dd5d-634f-7896-f37d1c8f4e85@michael-ring.org> Message-ID: On 20/11/2018 22:44, Michael Ring via lazarus wrote: > There is only one issue I see at the moment, the debugger is a global > setting, afaik I cannot change the debugger configuration based on a > project. > > The problem is that for debugging arm I will have to use > arm-none-eabi-gdb, for pic32 I will have to use mips-sde-elf-gdb for > debugging and both will have to use a special debugger class for > interfacing with Segger JLink Debug Probe and possibly openocd in the > future. > > Other people, that use Lazaeus for Windows/Linux/Mac Development would > also need to change the global setting when switching from embedded > development to native development to the default gdb debugger. > > What is the best way to implement this project based override, I guess > I can do the coding myself as I have also created my own debugger for > JLink, but I do not know how to do this debugger switching in the > proper 'Lazarus' way..... Indeed an issue that several people raised.... Well first of all, it depends on how much work you want to spent. There are several approaches possible. Just some initial thoughts, ideas are welcome... * All of them should really refactor the "debugger setting" related stuff from the big TEnvironmentOptions class into its own class, so that it can be re-used as needed. Some details are more than what would be really required to have a working version. Up to you how far you want to go. (I got a bit carried away while typing) 1) Have an override in the project. All the settings can be stored there too. That may require duplication of the frontend, so the project options can show the same setting page. Not my favourite (and not sure if the least work) 2) Expand the TEnvironmentOptions, so they can have a list of named options. The project then chooses by name/ID (for each buildmode). - That just adds a name dropdown / add/del button to the existing config. - The config must then be stored like the units in the project lpi, each config in a different path.   The current path   would then be replaced by     The EnvOptsVersion would be increased so code knows what to load. The DebugManager would ask the TEnvironmentOptions via TEnvironmentOptions.GetDebuggerConfByName(name) and get the refactored/extracted object that holds all the debugger setting. So outside the TEnvironmentOptions changes will be minimal. (Hopefully) - Name or ID could be used. This has an impact when projects are shared between people.   It needs some additional thought what to do, if a name/id is not found.   Also names have the issue, that the same name, does not guarantee the same settings.   ID could be UUID, but then you would never have the correct settings for some one else's project. And you cant change the UUID in the lpi (or the other person has a problem), so you must create the same ID in your TEnvironmentOptions....,  Maybe storing (in the lpi) a name, with DebuggerType/Class (eg GDBMI) and optional an ID. Then if you do not have the ID, you can import it, to any of your configs (so each config in TEnvironmentOptions can have many IDs) - Optional/Later: there could be an option where to save the setting EnvironmentOptions/project.lpi/project.lps   But it would still be the TEnvironmentOptions responsibility to coordinate everything.   Note that some setting, like Ignored-Exceptions are already on the project. They do not need to be affected. 3) Your idea? ----------------- I like the 2nd, but please bring forward any thoughts you have. Let me know your ideas, and what you think is plausible for you to do, and we can look at implementation details. *** Also despite me bringing forward various options, not all of them will be required. *** *** E.g you could deliver a working version using just a name list in EnvironmentOptions. And a name in the project. Thats afaik the minimum needed *** From mlistft at mail.ru Wed Nov 21 01:17:20 2018 From: mlistft at mail.ru (=?UTF-8?B?RlR1cnRsZQ==?=) Date: Wed, 21 Nov 2018 03:17:20 +0300 Subject: [Lazarus] =?utf-8?q?IDE_Project_Options_-_icon_needed?= In-Reply-To: References: Message-ID: <1542759440.71826842@f523.i.mail.ru> > >Button "Load default" in Icon group - needs new icon, which is used for >"set default" buttons in IDE. it is brown curved arrow. > >-- >Regards, >Alexey > https://bugs.freepascal.org/view.php?id=34578 -- FTurtle -------------- next part -------------- An HTML attachment was scrubbed... URL: From d.ioannidis at nephelae.eu Wed Nov 21 10:58:36 2018 From: d.ioannidis at nephelae.eu (Dimitrios Chr. Ioannidis) Date: Wed, 21 Nov 2018 11:58:36 +0200 Subject: [Lazarus] Switching debugger based on Project settings for embedded targets In-Reply-To: <30238cc9-dd5d-634f-7896-f37d1c8f4e85@michael-ring.org> References: <30238cc9-dd5d-634f-7896-f37d1c8f4e85@michael-ring.org> Message-ID: Hi, On 2018-11-20 23:44, Michael Ring via lazarus wrote: > What is the best way to implement this project based override, I guess > I can do the coding myself as I have also created my own debugger for > JLink, but I do not know how to do this debugger switching in the > proper 'Lazarus' way..... I would like to be involved / help as I am thinking implementing the mEDBG protocol and intergrate it to Lazarus to debug AVR MCU's using this debugger https://hackaday.io/project/162372-xplained-yourself . I already tried to use the avr-gdb --> avarice --> dragon --> atmegaxxx combination ( which worked in Linux but not in Windows ) and the result is that I have 3 bricked mcu's ( most probably by flashes has been worn out by software breakpoints) . Not even the HVPP procedure restore them. Anyway if I can help ( and learn at the same time the Lazarus / Debug internals ) that would be awesome. regards, -- Dimitrios Chr. Ioannidis From mailinglists at geldenhuys.co.uk Wed Nov 21 11:30:52 2018 From: mailinglists at geldenhuys.co.uk (Graeme Geldenhuys) Date: Wed, 21 Nov 2018 10:30:52 +0000 Subject: [Lazarus] what can we do to get a better debugger In-Reply-To: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> References: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> Message-ID: <1dc033be-a578-d2f8-ca20-e53b252e4cb5@geldenhuys.co.uk> On 2018-11-20 10:37 a.m., Dennis via lazarus wrote: > Shall we start a fund raising event to raise fund for a new and better > debugger for FPC + Lazarus? Indeed, the debugger is the weakest part of FPC/Lazarus development tools. The problem is not so much funding the idea of implementing a dedicated and improved debugger. There has been many attempts at implementing new debuggers (all without funding) and some of that have now been combined into one Pascal based debugger (fpdebug). The real problem is man-power - finding someone that can give their full attention to the task until it is complete (and hopefully on par with debuggers like can be seen in Java development). With small open source projects like FPC and Lazarus it is hard to find such dedicated man-power, because most contributors actually have full time jobs, or get bored and work on other areas they find more enjoyable. Regards, Graeme -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/ My public PGP key: http://tinyurl.com/graeme-pgp From joost at cnoc.nl Wed Nov 21 13:08:01 2018 From: joost at cnoc.nl (Joost van der Sluis) Date: Wed, 21 Nov 2018 13:08:01 +0100 Subject: [Lazarus] what can we do to get a better debugger In-Reply-To: <91f961f8-c5e6-1dff-bfa0-9dc1f1cfc08d@mfriebe.de> References: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> <91f961f8-c5e6-1dff-bfa0-9dc1f1cfc08d@mfriebe.de> Message-ID: Op 20-11-18 om 12:19 schreef Martin Frb via lazarus: > On 20/11/2018 11:37, Dennis via lazarus wrote: >> FPC and Lazarus are great but the GDB is inadequate. >> Many times in my development, GDB failed or crashed, especially when I >> am debugging multi thread programs. >> >> Shall we start a fund raising event to raise fund for a new and better >> debugger for FPC + Lazarus? (provided there are talents out there who >> would do implement it). > > That work is already in process (though very slowly / work has > started/stopped plenty of times over the past many years). It is called > FpDebug. > Donations are still welcome. > Under Windows and Linux you can install the package LazDebuggerFp. (You > can do on Mac too, but then you need to codesign the entire IDE). > Best use Lazarus trunk (it is already ahead of fixes 2.0 branch, but by > very little only) You do not have to sign the ide. You can use FpDebug as external debugger, then you only have to sigh the FpDebug executable itself. > Support for threaded apps in fpdebug is not yet there. > Under Linux only the main thread is debugged. Windows has bare minimum > (and untested) support for dealing with threads. Strange, debugging threads works fine. At least on Linux and OS/X. There were some memory-leaks in the show-threads window, though. I've asked you to look at it. Everyone who wants to help improving the debugger, should stop working with gdb and install fpdebug. And start filling bugs. Fpdebug is already better in many aspects then gdb, only now and then I have to switch back to gdb. Regards, Joost. From joost at cnoc.nl Wed Nov 21 13:15:35 2018 From: joost at cnoc.nl (Joost van der Sluis) Date: Wed, 21 Nov 2018 13:15:35 +0100 Subject: [Lazarus] what can we do to get a better debugger In-Reply-To: <1dc033be-a578-d2f8-ca20-e53b252e4cb5@geldenhuys.co.uk> References: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> <1dc033be-a578-d2f8-ca20-e53b252e4cb5@geldenhuys.co.uk> Message-ID: <93daec8c-7c12-1b47-7048-50fce11d1174@cnoc.nl> Op 21-11-18 om 11:30 schreef Graeme Geldenhuys via lazarus: > On 2018-11-20 10:37 a.m., Dennis via lazarus wrote: > Indeed, the debugger is the weakest part of FPC/Lazarus development tools. I don't agree. The lack of a good (online) package-system is the weakest part. (debugging might be the second) > The real problem is man-power - finding someone that can give their full > attention to the task until it is complete (and hopefully on par with > debuggers like can be seen in Java development). With small open source > projects like FPC and Lazarus it is hard to find such dedicated > man-power, because most contributors actually have full time jobs, or > get bored and work on other areas they find more enjoyable. It is fairly simple: my top priorities are now: 1: Fpmake/Fppkg 2: Fpdebug 3: Attributes / RTTI I decided to work only on Fpmake and Fppkg. When that works, switch to Fpdebug. And then the attributes. I hope that someone else can pick up the attributes and RTTI work, though. A lot is already happening in this regard. And Fpdebug works fine. This is also something that others can help with. Martin does most of the Lazarus-stuff and everything needed to show variables and such. I'm working on the lower-level parts. But, as Graeme said, all in my spare time. Regards, Joost From lazarus at mfriebe.de Wed Nov 21 13:25:37 2018 From: lazarus at mfriebe.de (Martin Frb) Date: Wed, 21 Nov 2018 13:25:37 +0100 Subject: [Lazarus] mEDBG Debugger [[was: Re: Switching debugger based on Project settings for embedded targets]] In-Reply-To: References: <30238cc9-dd5d-634f-7896-f37d1c8f4e85@michael-ring.org> Message-ID: <3823ba3d-0090-38cf-f10b-304faf290256@mfriebe.de> On 21/11/2018 10:58, Dimitrios Chr. Ioannidis via lazarus wrote: >   I would like to be involved / help as I am thinking implementing the > mEDBG protocol and intergrate it to Lazarus to debug AVR MCU's using > this debugger https://hackaday.io/project/162372-xplained-yourself . > >   I already tried to use the avr-gdb --> avarice --> dragon --> > atmegaxxx combination ( which worked in Linux but not in Windows ) and > the result is that I have 3 bricked mcu's ( most probably by flashes > has been worn out by software breakpoints) . Not even the HVPP > procedure restore them. > >   Anyway if I can help ( and learn at the same time the Lazarus / > Debug internals ) that would be awesome. The Debugger in Lazarus consists of 2 layers (plus the external exe, if based on one) The presentation and IDE control: DebugManager/DebugBoss The BackEnd: LazDebuggerGDBMI, and others. You would need a new backend. Backends are based on the DebuggerInterface components\debuggerintf\... This is not yet documented. (And may still be subject to small changes). [Actually someone started to put something on the wiki, I dont know if that has gone anywhere ...., I recommend to look at example code, see below] The easiest way for you is to look at an existing implementation, and replace the communication with the external exe. The "simplest" available is: components\lazdebuggers\lazdebuggerlldb\lazdebuggerlldb.lpk And you can go back in SVN to its initial revisions, to get an even simpler version. Depending on how your external exe works, you need some sort of control when to send which message, and how to parse the answers... "lazdebuggerlldb" has 2 internal queues: - One in commandline debugger, which controls sending individual commands, and waiting for answers. - One in  the main lazdebuggerlldb, which is hard to explain: The truth is, it shouldn't be a queue, it is a poor replacement for a state. (It happens to be as it is, because it was copied from the gdbmi debugger....). Its purpose is to ensure, that watches do not run, while the target is running, or step/run is not done while evaluating a watch. So basically if an "action" (that may consists of one or many commands to the external exe) needs to wait for the correct debuggerstate, then that somehow happens here. Not all actions need to wait, so they may bypass that queue..... To start with ignore the inner queue, and send your commands directly to the external exe. Once you can do that, you can start thinking about coordinating the bigger picture. From lazarus at mfriebe.de Wed Nov 21 13:42:48 2018 From: lazarus at mfriebe.de (Martin Frb) Date: Wed, 21 Nov 2018 13:42:48 +0100 Subject: [Lazarus] what can we do to get a better debugger In-Reply-To: References: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> <91f961f8-c5e6-1dff-bfa0-9dc1f1cfc08d@mfriebe.de> Message-ID: On 21/11/2018 13:08, Joost van der Sluis via lazarus wrote: > Op 20-11-18 om 12:19 schreef Martin Frb via lazarus: >> >> That work is already in process (though very slowly / work has >> started/stopped plenty of times over the past many years). It is >> called FpDebug. >> Donations are still welcome. >> Under Windows and Linux you can install the package LazDebuggerFp. >> (You can do on Mac too, but then you need to codesign the entire IDE). >> Best use Lazarus trunk (it is already ahead of fixes 2.0 branch, but >> by very little only) > > You do not have to sign the ide. You can use FpDebug as external > debugger, then you only have to sigh the FpDebug executable itself. I wasn't sure if that is fully working... What class/package is that in the IDE? > >> Support for threaded apps in fpdebug is not yet there. >> Under Linux only the main thread is debugged. Windows has bare >> minimum  (and untested) support for dealing with threads. > > Strange, debugging threads works fine. At least on Linux and OS/X. > There were some memory-leaks in the show-threads window, though. I've > asked you to look at it. When I tested (last week), using "Pause" button, only the main thread stopped. There was no way to pause the other threads. Each one of them would stop, if reaching a breakpoint. But then the main thread (and others) would continues running. If I had a test thread, that loops an a single "a:=1;" (consuming cpu like hell), and I try to set a breakpoint, I got occasional crashes of the debugged exe. (Not verified, I think it pauses the main thread while setting the breakpoint?, but the sub thread in which the breakpoint will be set, is still running...). Need to dig deeper into that. So need to check, about pausing all threads. -------- A good way to find thread issues, is to debug the IDE, and inside the debugged IDE compile your project (uses thread), and then debug your project (does fork processes). From d.ioannidis at nephelae.eu Wed Nov 21 14:09:35 2018 From: d.ioannidis at nephelae.eu (Dimitrios Chr. Ioannidis) Date: Wed, 21 Nov 2018 15:09:35 +0200 Subject: [Lazarus] mEDBG Debugger [[was: Re: Switching debugger based on Project settings for embedded targets]] In-Reply-To: <3823ba3d-0090-38cf-f10b-304faf290256@mfriebe.de> References: <30238cc9-dd5d-634f-7896-f37d1c8f4e85@michael-ring.org> <3823ba3d-0090-38cf-f10b-304faf290256@mfriebe.de> Message-ID: <3f2b8a639e0b4739f79b662ec4705ba6@nephelae.eu> Hi, thx for the info ! On 2018-11-21 14:25, Martin Frb via lazarus wrote: > Depending on how your external exe works, you need some sort of > control when to send which message, and how to parse the answers... Actually I'll communicate with the HW Debugger using mEDBG Protocol via Serial ( USB CDC ). So no external exe. Again thx for the info ! regards, -- Dimitrios Chr. Ioannidis From lazarus at mfriebe.de Wed Nov 21 14:28:19 2018 From: lazarus at mfriebe.de (Martin Frb) Date: Wed, 21 Nov 2018 14:28:19 +0100 Subject: [Lazarus] mEDBG Debugger [[was: Re: Switching debugger based on Project settings for embedded targets]] In-Reply-To: <3f2b8a639e0b4739f79b662ec4705ba6@nephelae.eu> References: <30238cc9-dd5d-634f-7896-f37d1c8f4e85@michael-ring.org> <3823ba3d-0090-38cf-f10b-304faf290256@mfriebe.de> <3f2b8a639e0b4739f79b662ec4705ba6@nephelae.eu> Message-ID: <1c4c47a3-8dee-bd28-6f94-3bb128e3ca74@mfriebe.de> On 21/11/2018 14:09, Dimitrios Chr. Ioannidis via lazarus wrote: > Hi, > >   thx for the info ! > > On 2018-11-21 14:25, Martin Frb via lazarus wrote: >> Depending on how your external exe works, you need some sort of >> control when to send which message, and how to parse the answers... > >   Actually I'll communicate with the HW Debugger using mEDBG Protocol > via Serial ( USB CDC ). So no external exe. > >   Again thx for the info ! Well then you probably will need to look at the various FpDebug based debuggers too. FpDebug can read the dwarf info. You will need to implement run/pause/breakpoint (there is something in fpdebug, but I do not know if that works for you). And then provide memory access, so fpdebug can read data, to evaluate watches. From joost at cnoc.nl Wed Nov 21 14:55:03 2018 From: joost at cnoc.nl (Joost van der Sluis) Date: Wed, 21 Nov 2018 14:55:03 +0100 Subject: [Lazarus] what can we do to get a better debugger In-Reply-To: References: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> <91f961f8-c5e6-1dff-bfa0-9dc1f1cfc08d@mfriebe.de> Message-ID: <7238330b-d6d8-d4ff-4d05-caf0b5e1de87@cnoc.nl> Op 21-11-18 om 13:42 schreef Martin Frb via lazarus: > On 21/11/2018 13:08, Joost van der Sluis via lazarus wrote: >> Op 20-11-18 om 12:19 schreef Martin Frb via lazarus: >>> >>> That work is already in process (though very slowly / work has >>> started/stopped plenty of times over the past many years). It is >>> called FpDebug. >>> Donations are still welcome. >>> Under Windows and Linux you can install the package LazDebuggerFp. >>> (You can do on Mac too, but then you need to codesign the entire IDE). >>> Best use Lazarus trunk (it is already ahead of fixes 2.0 branch, but >>> by very little only) >> >> You do not have to sign the ide. You can use FpDebug as external >> debugger, then you only have to sigh the FpDebug executable itself. > I wasn't sure if that is fully working... > > What class/package is that in the IDE? You have to install lazdebuggerfpdserver.lpk. The host-application can be found in components/fpdebug/app/fpdserver. This is the one that should be signed. This once was the first version of fpdebug that I've got running. But I'm not sure what it's state is at this moment. >> >>> Support for threaded apps in fpdebug is not yet there. >>> Under Linux only the main thread is debugged. Windows has bare >>> minimum  (and untested) support for dealing with threads. >> >> Strange, debugging threads works fine. At least on Linux and OS/X. >> There were some memory-leaks in the show-threads window, though. I've >> asked you to look at it. > When I tested (last week), using "Pause" button, only the main thread > stopped. There is no option to choose which thread you want to stop, no? > There was no way to pause the other threads. > > Each one of them would stop, if reaching a breakpoint. But then the main > thread (and others) would continues running. True. Only one thread stops. (I thought this was neat!) You want all threads to stop when one of them stops? Always? I'm wondering which layer we should let take care of this. It would be nice if the user can decide which threads should stop or continue. In that case we need to adapt the abstraction-layer and an update of the GUI. > If I had a test thread, that loops an a single "a:=1;" (consuming cpu > like hell), and I try to set a breakpoint, I got occasional crashes of > the debugged exe. (Not verified, I think it pauses the main thread while > setting the breakpoint?, but the sub thread in which the breakpoint will > be set, is still running...). Ah, yes. Offcourse. When you set a breakpoint while the application is running, we have to pause the application. At the moment it will only pause the main thread, which means that when another thread touches the code we want to set the breakpoint on... big trouble. Issues like these, that's why we need more testing. Regards, Joost. From mail at michael-ring.org Wed Nov 21 15:02:33 2018 From: mail at michael-ring.org (Michael Ring) Date: Wed, 21 Nov 2018 15:02:33 +0100 Subject: [Lazarus] mEDBG Debugger [[was: Re: Switching debugger based on Project settings for embedded targets]] In-Reply-To: <1c4c47a3-8dee-bd28-6f94-3bb128e3ca74@mfriebe.de> References: <30238cc9-dd5d-634f-7896-f37d1c8f4e85@michael-ring.org> <3823ba3d-0090-38cf-f10b-304faf290256@mfriebe.de> <3f2b8a639e0b4739f79b662ec4705ba6@nephelae.eu> <1c4c47a3-8dee-bd28-6f94-3bb128e3ca74@mfriebe.de> Message-ID: I can also provide you my implementation for JLink-Debugger if it helps, thanks to some great improovements Martin did in the past the code I needed to add was reduced to a minimum, and I am now checking if I need my own implementation at all.... Michael Am 21.11.18 um 14:28 schrieb Martin Frb via lazarus: > On 21/11/2018 14:09, Dimitrios Chr. Ioannidis via lazarus wrote: >> Hi, >> >>   thx for the info ! >> >> On 2018-11-21 14:25, Martin Frb via lazarus wrote: >>> Depending on how your external exe works, you need some sort of >>> control when to send which message, and how to parse the answers... >> >>   Actually I'll communicate with the HW Debugger using mEDBG Protocol >> via Serial ( USB CDC ). So no external exe. >> >>   Again thx for the info ! > > Well then you probably will need to look at the various FpDebug based > debuggers too. > > FpDebug can read the dwarf info. You will need to implement > run/pause/breakpoint (there is something in fpdebug, but I do not know > if that works for you). > And then provide memory access, so fpdebug can read data, to evaluate > watches. > From lazarus at mfriebe.de Wed Nov 21 16:40:23 2018 From: lazarus at mfriebe.de (Martin Frb) Date: Wed, 21 Nov 2018 16:40:23 +0100 Subject: [Lazarus] what can we do to get a better debugger In-Reply-To: <7238330b-d6d8-d4ff-4d05-caf0b5e1de87@cnoc.nl> References: <13fcb401-058b-6bca-02a6-db7c627a9efe@avidsoft.com.hk> <91f961f8-c5e6-1dff-bfa0-9dc1f1cfc08d@mfriebe.de> <7238330b-d6d8-d4ff-4d05-caf0b5e1de87@cnoc.nl> Message-ID: On 21/11/2018 14:55, Joost van der Sluis via lazarus wrote: >> When I tested (last week), using "Pause" button, only the main thread >> stopped. > > There is no option to choose which thread you want to stop, no? Not that I have seen. I think (just a feeling/ no evidence) the debugger (in linux-classes) will need to loop through all the threads. Also need to verify if we distinguish, between thread and fork >> There was no way to pause the other threads. >> >> Each one of them would stop, if reaching a breakpoint. But then the >> main thread (and others) would continues running. > > True. Only one thread stops. (I thought this was neat!) You want all > threads to stop when one of them stops? Always? Hitting the Pause button, usually yes. Hitting a breakpoint, likely too, at least as default. Once paused, single stepping should (if OS supports / Linux does; Windows does not) offer to keep other threads paused, or to run them until the step finishes. > I'm wondering which layer we should let take care of this. It would be > nice if the user can decide which threads should stop or continue. In > that case we need to adapt the abstraction-layer and an update of the > GUI. Afaik, even GDB can do the single stepping choice above. So yes, that needs eventually to go to the GUI From skalogryz.lists at gmail.com Wed Nov 21 16:43:46 2018 From: skalogryz.lists at gmail.com (Dmitry Boyarintsev) Date: Wed, 21 Nov 2018 10:43:46 -0500 Subject: [Lazarus] editorconfig support Message-ID: Hello, if anyone is interested, I've started a support of editorconfig https://github.com/skalogryz/editorConfig for Pascal in general (which you can use in your editor project), as well as Lazarus IDE extension thanks, Dmitry -------------- next part -------------- An HTML attachment was scrubbed... URL: From mail at michael-ring.org Wed Nov 21 17:34:38 2018 From: mail at michael-ring.org (Michael Ring) Date: Wed, 21 Nov 2018 17:34:38 +0100 Subject: [Lazarus] Switching debugger based on Project settings for embedded targets In-Reply-To: References: <30238cc9-dd5d-634f-7896-f37d1c8f4e85@michael-ring.org> Message-ID: <8144e0fe-037b-2a68-70c1-257176ef189a@michael-ring.org> Hi Martin, thank you for the detailled answer. I like your idea of creating Id's for debugger configurations and as I want to go step by step (and I have great respect of 130kBytes of code in TEnvironmentOptions) I wanted to start small and grow as I go..... I am tempted to give the full refactoring a pass 8-) and prefer your option 2) So I thought about how to create a usefull Id and came up with the following: first part could be CRC16 of the Caption (to define the pricipal debugger Module that is used): GNU debugger (gdb) --> 0x167E GNU debugger through SSH (gdb) --> 0xB2AE GNU remote debugger (gdbserver) --> 0x5579 GNU remote debugger via jlink (jlinkgdbserver) --> 0x463C then add CRC16 of lowercase basename of gdb used: gdb --> 0x84FD mips-sde-elf-gdb -->0x7B4E arm-none-eabi-gdb -->0xB5E7 and then we could add a CRC32 of all options changed from default (or CRC32 of all options) so an id could look like this: 167E-84FD-FFFFFFFF for native debugger using gdb 5579-7B4E-FFFFFFFF for gdbserver using mips version of gdb This would allow us to always select the right debugger module by looking at the first 4 chars, and for people working together there is a high chance that also the debugger part matches. We can of course fill this up to look like a propper UUID..... That's already a reasonable starting point for a good configuration. We can tell the user (if we want to) that the debugger component used in the project cannot be found, we can also preconfigur the right debugger component when we find it and hint that the proper gdb is not jet configured. Not perfect, but this hopefully already covers a number of usecases. The real fun starts with also Checksumming the changes/all options, this allows us to pinpoint the exact configuration needed meaning that a developer will always get the perfect configuration for his own debug task. I first thought to explicity checksum even more fields (like Debugger_Remote_Port) but as there is no way back from a checksum to an actual setting I think it does not add much more benefit. What do you guys think? Michael Am 21.11.18 um 10:58 schrieb Dimitrios Chr. Ioannidis via lazarus: > Hi, > > On 2018-11-20 23:44, Michael Ring via lazarus wrote: >> What is the best way to implement this project based override, I guess >> I can do the coding myself as I have also created my own debugger for >> JLink, but I do not know how to do this debugger switching in the >> proper 'Lazarus' way..... > >   I would like to be involved / help as I am thinking implementing the > mEDBG protocol and intergrate it to Lazarus to debug AVR MCU's using > this debugger https://hackaday.io/project/162372-xplained-yourself . > >   I already tried to use the avr-gdb --> avarice --> dragon --> > atmegaxxx combination ( which worked in Linux but not in Windows ) and > the result is that I have 3 bricked mcu's ( most probably by flashes > has been worn out by software breakpoints) . Not even the HVPP > procedure restore them. > >   Anyway if I can help ( and learn at the same time the Lazarus / > Debug internals ) that would be awesome. > > regards, > From lazarus at mfriebe.de Wed Nov 21 19:16:37 2018 From: lazarus at mfriebe.de (Martin Frb) Date: Wed, 21 Nov 2018 19:16:37 +0100 Subject: [Lazarus] Switching debugger based on Project settings for embedded targets In-Reply-To: <8144e0fe-037b-2a68-70c1-257176ef189a@michael-ring.org> References: <30238cc9-dd5d-634f-7896-f37d1c8f4e85@michael-ring.org> <8144e0fe-037b-2a68-70c1-257176ef189a@michael-ring.org> Message-ID: <82de4493-2835-be54-8e9b-17e9d7419395@mfriebe.de> On 21/11/2018 17:34, Michael Ring via lazarus wrote: > Hi Martin, thank you for the detailled answer. > > I like your idea of creating Id's for debugger configurations and as I > want to go step by step (and I have great respect of 130kBytes of code > in TEnvironmentOptions) I wanted to start small and grow as I go..... > I am tempted to give the full refactoring a pass 8-) and prefer your > option 2) good :) > first part could be CRC16 of the Caption (to define the pricipal > debugger Module that is used): > GNU debugger (gdb) --> 0x167E I prefer human readable: TGDBMIDebugger, TSSHGDBMIDebugger, ... > then add CRC16 of lowercase basename of gdb used: > gdb --> 0x84FD > mips-sde-elf-gdb -->0x7B4E That fails, for example some of my gdb are called gdb_7_7.exe And FpDebug does not have an external exe at all. > This would allow us to always select the right debugger module by > looking at the first 4 chars, and for people working together there is > a high chance that also the debugger part matches. We can of course > fill this up to look like a propper UUID..... The above considerations are fine, if you look at a project that needs a very special debugger (for which there may be no alternative) But if you work as part of a team on a normal project, then one person may use gdb 7.7, another uses gdb 8.2, and yet another uses FpDebug. And they are all totally interchangeable. Anyway reading through this may have helped me to get some more clarity what may be needed. I did myself made it to complex in my first mail (late night mails...) ---------------- Overall, I would suggest to start, with a simple solution, For a single user there are 2 options - Name (human readable name, as given by user) - id (UUID) If you ever get another persons project, then what should happen (even if stored in session, the session could be in the lpi): - the name can accidentally match - the ID should never match => so you will be forced to choose a debugger So ID is better. And you don't need to include what kind of debugger to use (But see below). As developer you should know, that the target will run on FooBar, and you need a debugger that supports this ----------------- After some thought, I think - Store all debugger configs in the EnvironmentOpts, each with its own ID - use an ID  (in form of a UUID) - store the ID in the projects session (lps) That should be the base, and you can later add to this. I.e, all else should be optional. Once that works / Once the IDE can handle many configs => then you can look at the below options. ---------------- **For later ** Option 1: If you need to choose a debugger, and the IDE should be able to help you to get it right: => You can add a hint system. In the project settings/session this would look like    In LPS:      In LPI:   The Target depends on the TGDBMIDebugger class being able to return this info. Not sure how useful the exe name is. Hints can go into the project lpi. So the IDE can prompt you when the project is first opened. But then you set up your debugger as you need it, and store the ID in the lps (and the debugger config in the EnvironmentOpts) Option 2: Storing the entire config in the project lps. (It still should have an ID) It then is of course only available for that project. (like "Additions and Overrides" that can be stored IDE, lpi or lps) ** For even later** Storing in the lps will add another problem: even if the many settings can be transferred, the path to the external exe may be different on each PC. ---------------- Another issue is, what to do, if you get a project with an ID, that you do not have. - The user has to choose one of his debugger settings (or even create it) - But once you have chosen, and you write your ID back to the project, and commit it to svn/git, then all other team members must choose again.   => Well it should not happen. In such a case the ID should be in the session, and the session should not be in the repository. From svaa at ciberpiula.net Thu Nov 22 11:00:42 2018 From: svaa at ciberpiula.net (Santiago A.) Date: Thu, 22 Nov 2018 11:00:42 +0100 Subject: [Lazarus] Trying FPDebug Message-ID: <94a1453a-affc-a3a8-c88b-7cdf18388582@ciberpiula.net> Hello: I would like to fiddle a little with FPdebug, but I'm a little confused. I have lazarus 1.8.4 on window 7 32 bits I have installed the next packages FpDebug 0.0 lazdebuggerfp But that is not enough, it is still using GDB. isn't it? I have tried to install lazdebuggerfpdserver, but it needs baselinux and I am in win32. any tutorial or howto? -- Saludos Santiago A. From joost at cnoc.nl Thu Nov 22 11:08:22 2018 From: joost at cnoc.nl (Joost van der Sluis) Date: Thu, 22 Nov 2018 11:08:22 +0100 Subject: [Lazarus] Trying FPDebug In-Reply-To: <94a1453a-affc-a3a8-c88b-7cdf18388582@ciberpiula.net> References: <94a1453a-affc-a3a8-c88b-7cdf18388582@ciberpiula.net> Message-ID: Op 22-11-18 om 11:00 schreef Santiago A. via lazarus: > > I would like to fiddle a little with FPdebug, but I'm a little confused. > I have lazarus 1.8.4 on window 7 32 bits > > I have installed the next packages > > FpDebug 0.0 > lazdebuggerfp - Once you have installed lazdebuggerfp you have to go to the IDE-options. (not the package or project options, but the IDE-options) - Then select 'Debugger' on the left - Select 'FpDebug internal Dwarf-debugger (beta)' on the right Then you're done. Note that you have to select an executable, but this executable is never used by FpDebug, so you can leave it on 'gdb'. Regards, Joost. From bo.berglund at gmail.com Thu Nov 22 12:28:26 2018 From: bo.berglund at gmail.com (Bo Berglund) Date: Thu, 22 Nov 2018 12:28:26 +0100 Subject: [Lazarus] Lazarus installation problem on Raspberry Pi (localized to Swedish) Message-ID: <454dvdho3fv6dkeq2f87bn1vpt8h9sspoh@4ax.com> I have been asked to advice on a problem occurring when installing FPC/Lazarus on a Raspberry Pi device using a script I have published on-line. The script retrieves all sources via svn and also sets up the development environment using apt-get. It also downloads the seed fpc compiler ver 3.0.0 to use during the process. The user shows a part of the screen output when the failure happens during make bigide inside the source dir: (9009) Assembling main /home/pi/dev/lazarus/1.6/ide/lazarus.pp(71,5) Hint: (5023) Unit “FPCUnitTestRunner” not used in Lazarus (9009) Assembling lazarus /home/pi/dev/lazarus/1.6/ide/lazarus.pp(150,42) Error: (9008) Can’t call the assembler, error -1 switching to external assembling /home/pi/dev/lazarus/1.6/ide/lazarus.pp(150,42) Fatal: (10026) There were 2 errors compiling module, stopping Fatal: (1018) Compilation aborted Makefile:4004: receptet för målet ”lazarus” misslyckades Since this has worked for many users now I am wondering what could be the cause? One observation I did is that the messages include Swedish in the output, so clearly this box is localized to Sweden, which I have never tested. Could such a localization affect some aspect of the installation from sources? -- Bo Berglund Developer in Sweden From giuliano.colla at fastwebnet.it Thu Nov 22 13:00:21 2018 From: giuliano.colla at fastwebnet.it (Giuliano Colla) Date: Thu, 22 Nov 2018 13:00:21 +0100 Subject: [Lazarus] Lazarus installation problem on Raspberry Pi (localized to Swedish) In-Reply-To: <454dvdho3fv6dkeq2f87bn1vpt8h9sspoh@4ax.com> References: <454dvdho3fv6dkeq2f87bn1vpt8h9sspoh@4ax.com> Message-ID: Easy way to check: Launch the script using a different locale. E. G. : LANG=C ; whatever.sh If successful it is a matter of localization. If it fails, a matter of environment, such as missing binutils, or something of this kind. Giuliano Inviato da iPhone > Il giorno 22 nov 2018, alle ore 12:28, Bo Berglund via lazarus ha scritto: > > I have been asked to advice on a problem occurring when installing > FPC/Lazarus on a Raspberry Pi device using a script I have published > on-line. The script retrieves all sources via svn and also sets up the > development environment using apt-get. > It also downloads the seed fpc compiler ver 3.0.0 to use during the > process. > > The user shows a part of the screen output when the failure happens > during make bigide inside the source dir: > > (9009) Assembling main > > /home/pi/dev/lazarus/1.6/ide/lazarus.pp(71,5) Hint: (5023) Unit > “FPCUnitTestRunner” not used in Lazarus > > (9009) Assembling lazarus > > /home/pi/dev/lazarus/1.6/ide/lazarus.pp(150,42) Error: (9008) Can’t > call the assembler, error -1 switching to external assembling > > /home/pi/dev/lazarus/1.6/ide/lazarus.pp(150,42) Fatal: (10026) There > were 2 errors compiling module, stopping > > Fatal: (1018) Compilation aborted > Makefile:4004: receptet för målet ”lazarus” misslyckades > > Since this has worked for many users now I am wondering what could be > the cause? > > One observation I did is that the messages include Swedish in the > output, so clearly this box is localized to Sweden, which I have never > tested. > Could such a localization affect some aspect of the installation from > sources? > > > -- > Bo Berglund > Developer in Sweden > > -- > _______________________________________________ > lazarus mailing list > lazarus at lists.lazarus-ide.org > https://lists.lazarus-ide.org/listinfo/lazarus From giuliano.colla at fastwebnet.it Thu Nov 22 13:00:21 2018 From: giuliano.colla at fastwebnet.it (Giuliano Colla) Date: Thu, 22 Nov 2018 13:00:21 +0100 Subject: [Lazarus] Lazarus installation problem on Raspberry Pi (localized to Swedish) In-Reply-To: <454dvdho3fv6dkeq2f87bn1vpt8h9sspoh@4ax.com> References: <454dvdho3fv6dkeq2f87bn1vpt8h9sspoh@4ax.com> Message-ID: Easy way to check: Launch the script using a different locale. E. G. : LANG=C ; whatever.sh If successful it is a matter of localization. If it fails, a matter of environment, such as missing binutils, or something of this kind. Giuliano Inviato da iPhone > Il giorno 22 nov 2018, alle ore 12:28, Bo Berglund via lazarus ha scritto: > > I have been asked to advice on a problem occurring when installing > FPC/Lazarus on a Raspberry Pi device using a script I have published > on-line. The script retrieves all sources via svn and also sets up the > development environment using apt-get. > It also downloads the seed fpc compiler ver 3.0.0 to use during the > process. > > The user shows a part of the screen output when the failure happens > during make bigide inside the source dir: > > (9009) Assembling main > > /home/pi/dev/lazarus/1.6/ide/lazarus.pp(71,5) Hint: (5023) Unit > “FPCUnitTestRunner” not used in Lazarus > > (9009) Assembling lazarus > > /home/pi/dev/lazarus/1.6/ide/lazarus.pp(150,42) Error: (9008) Can’t > call the assembler, error -1 switching to external assembling > > /home/pi/dev/lazarus/1.6/ide/lazarus.pp(150,42) Fatal: (10026) There > were 2 errors compiling module, stopping > > Fatal: (1018) Compilation aborted > Makefile:4004: receptet för målet ”lazarus” misslyckades > > Since this has worked for many users now I am wondering what could be > the cause? > > One observation I did is that the messages include Swedish in the > output, so clearly this box is localized to Sweden, which I have never > tested. > Could such a localization affect some aspect of the installation from > sources? > > > -- > Bo Berglund > Developer in Sweden > > -- > _______________________________________________ > lazarus mailing list > lazarus at lists.lazarus-ide.org > https://lists.lazarus-ide.org/listinfo/lazarus From pch at ap-i.net Thu Nov 22 13:12:08 2018 From: pch at ap-i.net (Patrick Chevalley) Date: Thu, 22 Nov 2018 12:12:08 +0000 Subject: [Lazarus] Lazarus installation problem on Raspberry Pi (localized to Swedish) In-Reply-To: <454dvdho3fv6dkeq2f87bn1vpt8h9sspoh@4ax.com> References: <454dvdho3fv6dkeq2f87bn1vpt8h9sspoh@4ax.com> Message-ID: <4359979ea9a3b66e146cc32bcdbb9720@ap-i.net> This error "Can't call the assembler..." is because of insufficient memory with the RPi. Just add 1GB of swap and it will work. Patrick From bo.berglund at gmail.com Thu Nov 22 13:53:54 2018 From: bo.berglund at gmail.com (Bo Berglund) Date: Thu, 22 Nov 2018 13:53:54 +0100 Subject: [Lazarus] Lazarus installation problem on Raspberry Pi (localized to Swedish) References: <454dvdho3fv6dkeq2f87bn1vpt8h9sspoh@4ax.com> <4359979ea9a3b66e146cc32bcdbb9720@ap-i.net> Message-ID: <0i9dvddpu7h3v446purfrjs1802t50kuk3@4ax.com> On Thu, 22 Nov 2018 12:12:08 +0000, Patrick Chevalley via lazarus wrote: >This error "Can't call the assembler..." is because of insufficient memory with the RPi. >Just add 1GB of swap and it will work. Thanks, I had forgotten about this altogether. On my recent boxes (RPi3 units) this seems to have worked with the default 100 MB swap.... I have suggested the user to up swap to 100 MB while he builds the IDE. -- Bo Berglund Developer in Sweden From svaa at ciberpiula.net Thu Nov 22 16:08:30 2018 From: svaa at ciberpiula.net (Santiago A.) Date: Thu, 22 Nov 2018 16:08:30 +0100 Subject: [Lazarus] Trying FPDebug In-Reply-To: References: <94a1453a-affc-a3a8-c88b-7cdf18388582@ciberpiula.net> Message-ID: <631d3ac4-cae9-c70f-85e4-affb2fa8135c@ciberpiula.net> El 22/11/18 a las 11:08, Joost van der Sluis via lazarus escribió: > Op 22-11-18 om 11:00 schreef Santiago A. via lazarus: >> >> I would like to fiddle a little with FPdebug, but I'm a little >> confused. I have lazarus 1.8.4 on window 7 32 bits >> >> I have installed the next packages >> >> FpDebug 0.0 >> lazdebuggerfp > > - Once you have installed lazdebuggerfp you have to go to the > IDE-options. (not the package or project options, but the IDE-options) > - Then select 'Debugger' on the left > - Select 'FpDebug internal Dwarf-debugger (beta)' on the right > > Then you're done. Note that you have to select an executable, but this > executable is never used by FpDebug, so you can leave it on 'gdb'. Ok. Thanks. I was puzzled looking for a FpDebug Executable. By the way, I see "FpDebug internal Dwarf-debugger (alpha)". An (Alpha) version, not (beta) version as you said. Is there a newer version, a (beta), or did you mean (alpha)? -- Saludos Santiago A. From lazarus at mfriebe.de Thu Nov 22 18:11:04 2018 From: lazarus at mfriebe.de (Martin Frb) Date: Thu, 22 Nov 2018 18:11:04 +0100 Subject: [Lazarus] Trying FPDebug In-Reply-To: <631d3ac4-cae9-c70f-85e4-affb2fa8135c@ciberpiula.net> References: <94a1453a-affc-a3a8-c88b-7cdf18388582@ciberpiula.net> <631d3ac4-cae9-c70f-85e4-affb2fa8135c@ciberpiula.net> Message-ID: On 22/11/2018 16:08, Santiago A. via lazarus wrote: > > By the way, I see "FpDebug internal Dwarf-debugger (alpha)". An > (Alpha) version, not (beta) version as you said. Is there a newer > version, a (beta), or did you mean (alpha)? > As part of Lazarus 2.0RC it is beta. From aaa5500 at ya.ru Fri Nov 23 15:24:43 2018 From: aaa5500 at ya.ru (AlexeyT) Date: Fri, 23 Nov 2018 17:24:43 +0300 Subject: [Lazarus] With new Win32 manifest LongPathAware I cannot make long filename Message-ID: <659b8eb9-3251-5fd9-5c86-4270eeceed5b@ya.ru> This app cannot make 2nd folder (it can make 1st) and make file. Error on file saving. why? new manifest option is used. Win10. { TForm1 } const s1='w123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012';   base='c:\work\'; procedure TForm1.Button1Click(Sender: TObject); var f: TStringList; begin   ForceDirectories(base+s1+'\'+s1);   f:= tstringlist.create;   f.add('zzz');   f.SaveToFile(base+s1+'\'+s1+'\test.txt');   f.free; end; -- Regards, Alexey From michael at freepascal.org Fri Nov 23 15:52:48 2018 From: michael at freepascal.org (Michael Van Canneyt) Date: Fri, 23 Nov 2018 15:52:48 +0100 (CET) Subject: [Lazarus] With new Win32 manifest LongPathAware I cannot make long filename In-Reply-To: <659b8eb9-3251-5fd9-5c86-4270eeceed5b@ya.ru> References: <659b8eb9-3251-5fd9-5c86-4270eeceed5b@ya.ru> Message-ID: On Fri, 23 Nov 2018, AlexeyT via lazarus wrote: > This app cannot make 2nd folder (it can make 1st) and make file. Error > on file saving. why? new manifest option is used. Win10. > > { TForm1 } > > const > s1='w123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012'; >   base='c:\work\'; > > procedure TForm1.Button1Click(Sender: TObject); > var f: TStringList; > begin >   ForceDirectories(base+s1+'\'+s1); ForceDirectories is in the FPC RTL. It probably would need to obey the \\?\ prefix if long paths are to be supported. Michael. From aaa5500 at ya.ru Fri Nov 23 16:35:33 2018 From: aaa5500 at ya.ru (Alexey) Date: Fri, 23 Nov 2018 18:35:33 +0300 Subject: [Lazarus] With new Win32 manifest LongPathAware I cannot make long filename In-Reply-To: References: <659b8eb9-3251-5fd9-5c86-4270eeceed5b@ya.ru> Message-ID: <89942CC5-AD03-4581-8A16-EC7988BD972A@ya.ru> I turned new Ide manifest option (subj) on, so I can skip prefix, no? From listbox at martoks-place.de Fri Nov 23 22:55:57 2018 From: listbox at martoks-place.de (Martok) Date: Fri, 23 Nov 2018 22:55:57 +0100 Subject: [Lazarus] With new Win32 manifest LongPathAware I cannot make long filename In-Reply-To: <659b8eb9-3251-5fd9-5c86-4270eeceed5b@ya.ru> References: <659b8eb9-3251-5fd9-5c86-4270eeceed5b@ya.ru> Message-ID: Am 23.11.2018 um 15:24 schrieb AlexeyT via lazarus: > This app cannot make 2nd folder (it can make 1st) and make file. Error > on file saving. why? new manifest option is used. Win10. Does the same code work if you use the LongPathsEnabled registry setting? If so, there may be something off with the manifest... -- Regards, Martok Ceterum censeo b32079 esse sanandam. From dezlov at gmail.com Sat Nov 24 04:29:02 2018 From: dezlov at gmail.com (Denis Kozlov) Date: Sat, 24 Nov 2018 03:29:02 +0000 Subject: [Lazarus] With new Win32 manifest LongPathAware I cannot make long filename In-Reply-To: <659b8eb9-3251-5fd9-5c86-4270eeceed5b@ya.ru> References: <659b8eb9-3251-5fd9-5c86-4270eeceed5b@ya.ru> Message-ID: <763a5605-f922-bcdb-44a2-3c60396d3183@gmail.com> The new "Long path awareness" option is working! Apparently, you need to do both, embed the manifest and enable long paths in the registry or group policy. Only then you will be able to use long paths without the "\\?\" prefix. To enable via the Local Group Policy Editor, navigate to Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem> Enable Win32 long paths = Enabled. Tested on Windows 10, Lazarus 2.1.0 r59644, using RenameFile RTL routine. Regards, Denis On 23/11/2018 14:24, AlexeyT via lazarus wrote: > This app cannot make 2nd folder (it can make 1st) and make file. Error > on file saving. why? new manifest option is used. Win10. > > { TForm1 } > > const > s1='w123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012'; > >   base='c:\work\'; > > procedure TForm1.Button1Click(Sender: TObject); > var f: TStringList; > begin >   ForceDirectories(base+s1+'\'+s1); >   f:= tstringlist.create; >   f.add('zzz'); >   f.SaveToFile(base+s1+'\'+s1+'\test.txt'); >   f.free; > end; > From vojtech.cihak at atlas.cz Sun Nov 25 16:43:53 2018 From: vojtech.cihak at atlas.cz (=?utf-8?q?Vojt=C4=9Bch_=C4=8Cih=C3=A1k?=) Date: Sun, 25 Nov 2018 16:43:53 +0100 Subject: [Lazarus] =?utf-8?q?Order_of_OnCreate_and_OnActivate_in_Qt4?= Message-ID: <20181125164353.AD50F010@atlas.cz> Hi,   I met strange bug today. I have these lines in .lpr: ... Application.CreateForm(TFrmMain, FrmMain); ... Application.CreateForm(TFrmContext, FrmContext); ...   and the order of events in Qt and GTk2 is: FrmMain.Create FrmContext.Create FrmMain.Activate   Today I used tool qtconfig and changed style (Appearance) from Plastique to QtCurve. Now my code crashes, order of events is: FrmMain.Create FrmMain.Activate CRASH, because code in OnActivate assumes that FrmContext already exists.   So, Qt4+Plastique has different order of events than Qt4+QtCurve. Unfortunately, I cannot reproduce with simple demo.   What I'm doing wrong? Do I rely on something that is not guaranteed?   Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From zeljko at holobit.net Sun Nov 25 18:40:15 2018 From: zeljko at holobit.net (zeljko) Date: Sun, 25 Nov 2018 18:40:15 +0100 Subject: [Lazarus] Order of OnCreate and OnActivate in Qt4 In-Reply-To: <20181125164353.AD50F010@atlas.cz> References: <20181125164353.AD50F010@atlas.cz> Message-ID: <4283c630-c57f-8211-f31f-5686febffde8@holobit.net> On 11/25/2018 04:43 PM, Vojtěch Čihák via lazarus wrote: > Today I used tool qtconfig and changed style (Appearance) from Plastique > to QtCurve. Now my code crashes, order of events is: > > FrmMain.Create > > FrmMain.Activate > > CRASH, because code in OnActivate assumes that FrmContext already exists. > > So, Qt4+Plastique has different order of events than Qt4+QtCurve. > > Unfortunately, I cannot reproduce with simple demo. > > What I'm doing wrong? Do I rely on something that is not guaranteed? Afaik not, that should work w/o problems. Never seen such kind of problem with different themes. In any case, without example project I cannot help. zeljko From zeljko at holobit.net Sun Nov 25 18:40:15 2018 From: zeljko at holobit.net (zeljko) Date: Sun, 25 Nov 2018 18:40:15 +0100 Subject: [Lazarus] Order of OnCreate and OnActivate in Qt4 In-Reply-To: <20181125164353.AD50F010@atlas.cz> References: <20181125164353.AD50F010@atlas.cz> Message-ID: <4283c630-c57f-8211-f31f-5686febffde8@holobit.net> On 11/25/2018 04:43 PM, Vojtěch Čihák via lazarus wrote: > Today I used tool qtconfig and changed style (Appearance) from Plastique > to QtCurve. Now my code crashes, order of events is: > > FrmMain.Create > > FrmMain.Activate > > CRASH, because code in OnActivate assumes that FrmContext already exists. > > So, Qt4+Plastique has different order of events than Qt4+QtCurve. > > Unfortunately, I cannot reproduce with simple demo. > > What I'm doing wrong? Do I rely on something that is not guaranteed? Afaik not, that should work w/o problems. Never seen such kind of problem with different themes. In any case, without example project I cannot help. zeljko From zeljko at holobit.net Sun Nov 25 18:47:12 2018 From: zeljko at holobit.net (zeljko) Date: Sun, 25 Nov 2018 18:47:12 +0100 Subject: [Lazarus] Order of OnCreate and OnActivate in Qt4 In-Reply-To: <20181125164353.AD50F010@atlas.cz> References: <20181125164353.AD50F010@atlas.cz> Message-ID: <5e12acfb-1b62-645a-bfec-fa12adf96d6d@holobit.net> On 11/25/2018 04:43 PM, Vojtěch Čihák via lazarus wrote: > CRASH, because code in OnActivate assumes that FrmContext already exists. > > So, Qt4+Plastique has different order of events than Qt4+QtCurve. > > Unfortunately, I cannot reproduce with simple demo. > > What I'm doing wrong? Do I rely on something that is not guaranteed? Try to disable usage of QtNativeEventFilter in qtdefines.inc if it's enabled. zeljko From zeljko at holobit.net Sun Nov 25 18:47:12 2018 From: zeljko at holobit.net (zeljko) Date: Sun, 25 Nov 2018 18:47:12 +0100 Subject: [Lazarus] Order of OnCreate and OnActivate in Qt4 In-Reply-To: <20181125164353.AD50F010@atlas.cz> References: <20181125164353.AD50F010@atlas.cz> Message-ID: <5e12acfb-1b62-645a-bfec-fa12adf96d6d@holobit.net> On 11/25/2018 04:43 PM, Vojtěch Čihák via lazarus wrote: > CRASH, because code in OnActivate assumes that FrmContext already exists. > > So, Qt4+Plastique has different order of events than Qt4+QtCurve. > > Unfortunately, I cannot reproduce with simple demo. > > What I'm doing wrong? Do I rely on something that is not guaranteed? Try to disable usage of QtNativeEventFilter in qtdefines.inc if it's enabled. zeljko From badsectoracula at gmail.com Mon Nov 26 11:32:32 2018 From: badsectoracula at gmail.com (Kostas Michalopoulos) Date: Mon, 26 Nov 2018 11:32:32 +0100 Subject: [Lazarus] Order of OnCreate and OnActivate in Qt4 In-Reply-To: <5e12acfb-1b62-645a-bfec-fa12adf96d6d@holobit.net> References: <20181125164353.AD50F010@atlas.cz> <5e12acfb-1b62-645a-bfec-fa12adf96d6d@holobit.net> Message-ID: I wouldn't rely on event order as anything between the creation to Application.Run could call Application.ProcessMessages - including some components/controls you may be using. As a rule of thumb you should assume that after calling a control (or form) that it can start receiving events. In Qt4 styling is done through native code (QStyle subclasses) and it can alter widgets (QStyle::polish) so it isn't unthinkable that a theme could do something that generates events. On Sun, Nov 25, 2018 at 6:47 PM zeljko via lazarus < lazarus at lists.lazarus-ide.org> wrote: > On 11/25/2018 04:43 PM, Vojtěch Čihák via lazarus wrote: > > > CRASH, because code in OnActivate assumes that FrmContext already exists. > > > > So, Qt4+Plastique has different order of events than Qt4+QtCurve. > > > > Unfortunately, I cannot reproduce with simple demo. > > > > What I'm doing wrong? Do I rely on something that is not guaranteed? > > Try to disable usage of QtNativeEventFilter in qtdefines.inc if it's > enabled. > > zeljko > -- > _______________________________________________ > lazarus mailing list > lazarus at lists.lazarus-ide.org > https://lists.lazarus-ide.org/listinfo/lazarus > -------------- next part -------------- An HTML attachment was scrubbed... URL: From svaa at ciberpiula.net Mon Nov 26 12:18:42 2018 From: svaa at ciberpiula.net (Santiago A.) Date: Mon, 26 Nov 2018 12:18:42 +0100 Subject: [Lazarus] TDBNavigator enabled buttons Message-ID: Hello: I'm working with lazarus (Win32, 2.0 Rc2 + ZeosLib) When a not-readonly dataset is in browse state, all the buttons in navigator are enabled except post and cancel. When dataset enters in  edit or insert mode,  post and cancel are enabled and only edit button is disabled. I expected that while you are editing or inserting, all buttons except post and cancel would be disabled. I think I remember that delphi worked that way (I'm not sure, too many years ago). Anyway, Is there any option in navigator, or dataset, or datasource or anywhere to get such behavior, that is, disable all buttons except post and cancel? -- Saludos Santiago A. From vojtech.cihak at atlas.cz Mon Nov 26 15:29:36 2018 From: vojtech.cihak at atlas.cz (=?utf-8?q?Vojt=C4=9Bch_=C4=8Cih=C3=A1k?=) Date: Mon, 26 Nov 2018 15:29:36 +0100 Subject: [Lazarus] =?utf-8?q?Order_of_OnCreate_and_OnActivate_in_Qt4?= In-Reply-To: 00000000930b0002197001a34ff6 References: <20181125164353.AD50F010@atlas.cz>, <5e12acfb-1b62-645a-bfec-fa12adf96d6d@holobit.net> 00000000930b0002197001a34ff6 Message-ID: <20181126152936.03E620EB@atlas.cz> Thanks, Kostas, especially part about Qt styling.   I answered my solution yesterday, but it didn't appear in ML, it went to zejlko only - I noticed later. So here it is:   I don't have QtNativeEventFilter in qtdefines.inc at all. However, I found simple workaround. I create main form with Visible:=False; and when all other forms are created I do FrmMain.Show; (in *.lpr). The order of events is as expected.   Thanks.   ______________________________________________________________ > Od: "Kostas Michalopoulos via lazarus" > Komu: "Lazarus mailing list" > Datum: 26.11.2018 11:32 > Předmět: Re: [Lazarus] Order of OnCreate and OnActivate in Qt4 > I wouldn't rely on event order as anything between the creation to Application.Run could call Application.ProcessMessages - including some components/controls you may be using. As a rule of thumb you should assume that after calling a control (or form) that it can start receiving events.In Qt4 styling is done through native code (QStyle subclasses) and it can alter widgets (QStyle::polish) so it isn't unthinkable that a theme could do something that generates events. On Sun, Nov 25, 2018 at 6:47 PM zeljko via lazarus > wrote:On 11/25/2018 04:43 PM, Vojtěch Čihák via lazarus wrote: > CRASH, because code in OnActivate assumes that FrmContext already exists. > > So, Qt4+Plastique has different order of events than Qt4+QtCurve. > > Unfortunately, I cannot reproduce with simple demo. > > What I'm doing wrong? Do I rely on something that is not guaranteed? Try to disable usage of QtNativeEventFilter in qtdefines.inc if it's enabled. zeljko -- _______________________________________________ lazarus mailing list lazarus at lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus ---------- -- _______________________________________________ lazarus mailing list lazarus at lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus -------------- next part -------------- An HTML attachment was scrubbed... URL: From mail at michael-ring.org Tue Nov 27 11:25:46 2018 From: mail at michael-ring.org (Michael Ring) Date: Tue, 27 Nov 2018 11:25:46 +0100 Subject: [Lazarus] Lazarus not starting anymore since -r59627 on MacOSX Mojava x86_64 cocoa Message-ID: <3d33fe31-6248-2d0e-3fe2-2ab316c30ce6@michael-ring.org> The last working version is -r59626 after this I either received a crash, on latest trunk it take a little while until the crash is reported. removing the ~/.lazarus directory before starting does not help. (It sometimes helped in the past with similar issues) I have attached two crashlogs, 2nd one is from latest lazarus r59675 Michael Process:               lazarus [23273] Path: /usr/local/share/lazarus/lazarus.app/Contents/MacOS/lazarus Identifier:            lazarus.freepascal.ide Version:               2.1.0 (1) Code Type:             X86-64 (Native) Parent Process:        ??? [1] Responsible:           lazarus [23273] User ID:               501 Date/Time:             2018-11-27 10:00:47.021 +0100 OS Version:            Mac OS X 10.14.1 (18B75) Report Version:        12 Anonymous UUID:        6A731EE5-807E-5B80-F092-BF0389E45B2F Sleep/Wake UUID:       F8736D66-860C-444E-B4F2-D44621004FE6 Time Awake Since Boot: 84000 seconds Time Since Wake:       1200 seconds System Integrity Protection: enabled Crashed Thread:        0  Dispatch queue: com.apple.main-thread Exception Type:        EXC_CRASH (SIGABRT) Exception Codes:       0x0000000000000000, 0x0000000000000000 Exception Note:        EXC_CORPSE_NOTIFY Application Specific Information: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[TCocoaGroupBox setAllowsTruncatedLabels:]: unrecognized selector sent to instance 0x102a33900' terminating with uncaught exception of type NSException abort() called Application Specific Backtrace 1: 0   CoreFoundation                      0x00007fff4387ffa5 __exceptionPreprocess + 256 1   libobjc.A.dylib                     0x00007fff6f976efb objc_exception_throw + 48 2   CoreFoundation                      0x00007fff438fdc8d -[NSObject(NSObject) __retain_OA] + 0 3   CoreFoundation                      0x00007fff438215de ___forwarding___ + 1468 4   CoreFoundation                      0x00007fff43820f98 _CF_forwarding_prep_0 + 120 5   lazarus                             0x000000010030f8b7 COCOAWSCOMCTRLS$_$TCOCOAWSCUSTOMPAGE_$__$$_CREATEHANDLE$TWINCONTROL$TCREATEPARAMS$$TLCLINTFHANDLE + 143 6   lazarus                             0x0000000100236c62 CONTROLS$_$TWINCONTROL_$__$$_CREATEWND + 2194 7   lazarus                             0x00000001002363ce CONTROLS$_$TWINCONTROL_$__$$_CREATEHANDLE + 46 8   lazarus                             0x0000000100237ac7 CONTROLS$_$TWINCONTROL_$__$$_HANDLENEEDED + 119 9   lazarus                             0x0000000100237aa9 CONTROLS$_$TWINCONTROL_$__$$_HANDLENEEDED + 89 10  lazarus                             0x0000000100237aa9 CONTROLS$_$TWINCONTROL_$__$$_HANDLENEEDED + 89 11  lazarus                             0x0000000100237aa9 CONTROLS$_$TWINCONTROL_$__$$_HANDLENEEDED + 89 12  lazarus                             0x0000000100236a59 CONTROLS$_$TWINCONTROL_$__$$_CREATEWND + 1673 13  lazarus                             0x0000000100655ac9 ETMESSAGEFRAME$_$TMESSAGESCTRL_$__$$_CREATEWND + 25 14  lazarus                             0x00000001002363ce CONTROLS$_$TWINCONTROL_$__$$_CREATEHANDLE + 46 15  lazarus                             0x000000010022ff44 CONTROLS$_$TWINCONTROL_$__$$_UPDATESHOWING + 84 16  lazarus                             0x000000010022e65c CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 212 17  lazarus                             0x000000010022e61e CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 18  lazarus                             0x000000010022e61e CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 19  lazarus                             0x000000010022e61e CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 20  lazarus                             0x000000010022e61e CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 21  lazarus                             0x000000010022e61e CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 22  lazarus                             0x000000010022e61e CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 23  lazarus                             0x000000010022e61e CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 24  lazarus                             0x000000010022e61e CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 25  lazarus                             0x000000010022e454 CONTROLS$_$TWINCONTROL_$__$$_DOALLAUTOSIZE + 380 26  lazarus                             0x0000000100247db9 CONTROLS$_$TCONTROL_$__$$_ENABLEAUTOSIZING + 233 27  lazarus                             0x0000000100c6e2c7 ANCHORDOCKING$_$TANCHORDOCKMASTER_$__$$_ENABLEALLAUTOSIZING + 87 28  lazarus                             0x0000000100c6e834 ANCHORDOCKING$_$TANCHORDOCKMASTER_$__$$_FULLRESTORELAYOUT$TANCHORDOCKLAYOUTTREE$BOOLEAN$$BOOLEAN + 396 29  lazarus                             0x0000000100c8e0b9 ANCHORDESKTOPOPTIONS$_$TANCHORDESKTOPOPT_$__$$_RESTOREDESKTOP$$BOOLEAN + 41 30  lazarus                             0x00000001006e3f65 ENVIRONMENTOPTS$_$TDESKTOPOPT_$__$$_RESTOREDESKTOP + 69 31  lazarus                             0x000000010007d31c MAIN$_$TMAINIDE_$__$$_RESTOREIDEWINDOWS + 52 32  lazarus                             0x0000000100079211 MAIN$_$TMAINIDE_$__$$_STARTIDE + 409 33  lazarus                             0x000000010000160e PASCALMAIN + 534 34  lazarus                             0x0000000100021149 FPC_SYSTEMMAIN + 41 35  ???                                 0x0000000000000001 0x0 + 1 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0   libsystem_kernel.dylib            0x00007fff70b7cb86 __pthread_kill + 10 1   libsystem_pthread.dylib           0x00007fff70c32c50 pthread_kill + 285 2   libsystem_c.dylib                 0x00007fff70ae61c9 abort + 127 3   libc++abi.dylib                   0x00007fff6e170231 abort_message + 231 4   libc++abi.dylib                   0x00007fff6e1703cd default_terminate_handler() + 265 5   libobjc.A.dylib                   0x00007fff6f97932f _objc_terminate() + 97 6   libc++abi.dylib                   0x00007fff6e17bdfe std::__terminate(void (*)()) + 8 7   libc++abi.dylib                   0x00007fff6e17bbe2 __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 27 8   libc++abi.dylib                   0x00007fff6e16ebb9 __cxa_throw + 113 9   libobjc.A.dylib                   0x00007fff6f97703c objc_exception_throw + 369 10  com.apple.CoreFoundation          0x00007fff438fdc8d -[NSObject(NSObject) doesNotRecognizeSelector:] + 132 11  com.apple.CoreFoundation          0x00007fff438215de ___forwarding___ + 1468 12  com.apple.CoreFoundation          0x00007fff43820f98 _CF_forwarding_prep_0 + 120 13  lazarus.freepascal.ide            0x000000010030f8b7 COCOAWSCOMCTRLS$_$TCOCOAWSCUSTOMPAGE_$__$$_CREATEHANDLE$TWINCONTROL$TCREATEPARAMS$$TLCLINTFHANDLE + 143 (cocoawscomctrls.pas:464) 14  lazarus.freepascal.ide            0x0000000100236c62 CONTROLS$_$TWINCONTROL_$__$$_CREATEWND + 2194 (wincontrol.inc:7551) 15  lazarus.freepascal.ide            0x00000001002363ce CONTROLS$_$TWINCONTROL_$__$$_CREATEHANDLE + 46 (wincontrol.inc:7462) 16  lazarus.freepascal.ide            0x0000000100237ac7 CONTROLS$_$TWINCONTROL_$__$$_HANDLENEEDED + 119 (wincontrol.inc:7916) 17  lazarus.freepascal.ide            0x0000000100237aa9 CONTROLS$_$TWINCONTROL_$__$$_HANDLENEEDED + 89 (wincontrol.inc:7910) 18  lazarus.freepascal.ide            0x0000000100237aa9 CONTROLS$_$TWINCONTROL_$__$$_HANDLENEEDED + 89 (wincontrol.inc:7910) 19  lazarus.freepascal.ide            0x0000000100237aa9 CONTROLS$_$TWINCONTROL_$__$$_HANDLENEEDED + 89 (wincontrol.inc:7910) 20  lazarus.freepascal.ide            0x0000000100236a59 CONTROLS$_$TWINCONTROL_$__$$_CREATEWND + 1673 (wincontrol.inc:7531) 21  lazarus.freepascal.ide            0x0000000100655ac9 ETMESSAGEFRAME$_$TMESSAGESCTRL_$__$$_CREATEWND + 25 (etmessageframe.pas:1730) 22  lazarus.freepascal.ide            0x00000001002363ce CONTROLS$_$TWINCONTROL_$__$$_CREATEHANDLE + 46 (wincontrol.inc:7462) 23  lazarus.freepascal.ide            0x000000010022ff44 CONTROLS$_$TWINCONTROL_$__$$_UPDATESHOWING + 84 (wincontrol.inc:4404) 24  lazarus.freepascal.ide            0x000000010022e65c CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 212 (wincontrol.inc:3513) 25  lazarus.freepascal.ide            0x000000010022e61e CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 (wincontrol.inc:3507) 26  lazarus.freepascal.ide            0x000000010022e61e CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 (wincontrol.inc:3507) 27  lazarus.freepascal.ide            0x000000010022e61e CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 (wincontrol.inc:3507) 28  lazarus.freepascal.ide            0x000000010022e61e CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 (wincontrol.inc:3507) 29  lazarus.freepascal.ide            0x000000010022e61e CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 (wincontrol.inc:3507) 30  lazarus.freepascal.ide            0x000000010022e61e CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 (wincontrol.inc:3507) 31  lazarus.freepascal.ide            0x000000010022e61e CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 (wincontrol.inc:3507) 32  lazarus.freepascal.ide            0x000000010022e61e CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 (wincontrol.inc:3507) 33  lazarus.freepascal.ide            0x000000010022e454 CONTROLS$_$TWINCONTROL_$__$$_DOALLAUTOSIZE + 380 34  lazarus.freepascal.ide            0x0000000100247db9 CONTROLS$_$TCONTROL_$__$$_ENABLEAUTOSIZING + 233 35  lazarus.freepascal.ide            0x0000000100c6e2c7 ANCHORDOCKING$_$TANCHORDOCKMASTER_$__$$_ENABLEALLAUTOSIZING + 87 (anchordocking.pas:2265) 36  lazarus.freepascal.ide            0x0000000100c6e834 ANCHORDOCKING$_$TANCHORDOCKMASTER_$__$$_FULLRESTORELAYOUT$TANCHORDOCKLAYOUTTREE$BOOLEAN$$BOOLEAN + 396 37  lazarus.freepascal.ide            0x0000000100c8e0b9 ANCHORDESKTOPOPTIONS$_$TANCHORDESKTOPOPT_$__$$_RESTOREDESKTOP$$BOOLEAN + 41 (anchordesktopoptions.pas:299) 38  lazarus.freepascal.ide            0x00000001006e3f65 ENVIRONMENTOPTS$_$TDESKTOPOPT_$__$$_RESTOREDESKTOP + 69 (environmentopts.pp:1519) 39  lazarus.freepascal.ide            0x000000010007d31c MAIN$_$TMAINIDE_$__$$_RESTOREIDEWINDOWS + 52 (main.pp:2465) 40  lazarus.freepascal.ide            0x0000000100079211 MAIN$_$TMAINIDE_$__$$_STARTIDE + 409 (main.pp:1619) 41  lazarus.freepascal.ide            0x000000010000160e PASCALMAIN + 534 42  lazarus.freepascal.ide            0x0000000100021149 FPC_SYSTEMMAIN + 41 Crash from latest trunk: Process:               lazarus [61659] Path:                  /usr/local/share/lazarus/lazarus Identifier:            lazarus Version:               ??? Code Type:             X86-64 (Native) Parent Process:        ??? [1] Responsible:           lazarus [61659] User ID:               501 Date/Time:             2018-11-27 11:17:36.522 +0100 OS Version:            Mac OS X 10.14.1 (18B75) Report Version:        12 Anonymous UUID:        6A731EE5-807E-5B80-F092-BF0389E45B2F Sleep/Wake UUID:       F8736D66-860C-444E-B4F2-D44621004FE6 Time Awake Since Boot: 89000 seconds Time Since Wake:       6100 seconds System Integrity Protection: enabled Crashed Thread:        0  Dispatch queue: com.apple.main-thread Exception Type:        EXC_CRASH (SIGABRT) Exception Codes:       0x0000000000000000, 0x0000000000000000 Exception Note:        EXC_CORPSE_NOTIFY Application Specific Information: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[TCocoaGroupBox setAllowsTruncatedLabels:]: unrecognized selector sent to instance 0x102902ab0' terminating with uncaught exception of type NSException abort() called Application Specific Backtrace 1: 0   CoreFoundation                      0x00007fff4387ffa5 __exceptionPreprocess + 256 1   libobjc.A.dylib                     0x00007fff6f976efb objc_exception_throw + 48 2   CoreFoundation                      0x00007fff438fdc8d -[NSObject(NSObject) __retain_OA] + 0 3   CoreFoundation                      0x00007fff438215de ___forwarding___ + 1468 4   CoreFoundation                      0x00007fff43820f98 _CF_forwarding_prep_0 + 120 5   lazarus                             0x000000010030fbcf COCOAWSCOMCTRLS$_$TCOCOAWSCUSTOMPAGE_$__$$_CREATEHANDLE$TWINCONTROL$TCREATEPARAMS$$TLCLINTFHANDLE + 143 6   lazarus                             0x0000000100236f1a CONTROLS$_$TWINCONTROL_$__$$_CREATEWND + 2194 7   lazarus                             0x0000000100236686 CONTROLS$_$TWINCONTROL_$__$$_CREATEHANDLE + 46 8   lazarus                             0x0000000100237d7f CONTROLS$_$TWINCONTROL_$__$$_HANDLENEEDED + 119 9   lazarus                             0x0000000100237d61 CONTROLS$_$TWINCONTROL_$__$$_HANDLENEEDED + 89 10  lazarus                             0x0000000100237d61 CONTROLS$_$TWINCONTROL_$__$$_HANDLENEEDED + 89 11  lazarus                             0x0000000100237d61 CONTROLS$_$TWINCONTROL_$__$$_HANDLENEEDED + 89 12  lazarus                             0x0000000100236d11 CONTROLS$_$TWINCONTROL_$__$$_CREATEWND + 1673 13  lazarus                             0x0000000100656061 ETMESSAGEFRAME$_$TMESSAGESCTRL_$__$$_CREATEWND + 25 14  lazarus                             0x0000000100236686 CONTROLS$_$TWINCONTROL_$__$$_CREATEHANDLE + 46 15  lazarus                             0x00000001002301fc CONTROLS$_$TWINCONTROL_$__$$_UPDATESHOWING + 84 16  lazarus                             0x000000010022e914 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 212 17  lazarus                             0x000000010022e8d6 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 18  lazarus                             0x000000010022e8d6 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 19  lazarus                             0x000000010022e8d6 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 20  lazarus                             0x000000010022e8d6 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 21  lazarus                             0x000000010022e8d6 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 22  lazarus                             0x000000010022e8d6 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 23  lazarus                             0x000000010022e8d6 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 24  lazarus                             0x000000010022e8d6 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 25  lazarus                             0x000000010022e70c CONTROLS$_$TWINCONTROL_$__$$_DOALLAUTOSIZE + 380 26  lazarus                             0x0000000100248071 CONTROLS$_$TCONTROL_$__$$_ENABLEAUTOSIZING + 233 27  lazarus                             0x0000000100c6f02f ANCHORDOCKING$_$TANCHORDOCKMASTER_$__$$_ENABLEALLAUTOSIZING + 87 28  lazarus                             0x0000000100c6f59c ANCHORDOCKING$_$TANCHORDOCKMASTER_$__$$_FULLRESTORELAYOUT$TANCHORDOCKLAYOUTTREE$BOOLEAN$$BOOLEAN + 396 29  lazarus                             0x0000000100c8ee21 ANCHORDESKTOPOPTIONS$_$TANCHORDESKTOPOPT_$__$$_RESTOREDESKTOP$$BOOLEAN + 41 30  lazarus                             0x00000001006e45c5 ENVIRONMENTOPTS$_$TDESKTOPOPT_$__$$_RESTOREDESKTOP + 69 31  lazarus                             0x000000010007d42c MAIN$_$TMAINIDE_$__$$_RESTOREIDEWINDOWS + 52 32  lazarus                             0x0000000100079321 MAIN$_$TMAINIDE_$__$$_STARTIDE + 409 33  lazarus                             0x000000010000171e PASCALMAIN + 534 34  lazarus                             0x0000000100021259 FPC_SYSTEMMAIN + 41 35  ???                                 0x0000000000000001 0x0 + 1 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0   libsystem_kernel.dylib            0x00007fff70b7cb86 __pthread_kill + 10 1   libsystem_pthread.dylib           0x00007fff70c32c50 pthread_kill + 285 2   libsystem_c.dylib                 0x00007fff70ae61c9 abort + 127 3   libc++abi.dylib                   0x00007fff6e170231 abort_message + 231 4   libc++abi.dylib                   0x00007fff6e1703cd default_terminate_handler() + 265 5   libobjc.A.dylib                   0x00007fff6f97932f _objc_terminate() + 97 6   libc++abi.dylib                   0x00007fff6e17bdfe std::__terminate(void (*)()) + 8 7   libc++abi.dylib                   0x00007fff6e17bbe2 __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 27 8   libc++abi.dylib                   0x00007fff6e16ebb9 __cxa_throw + 113 9   libobjc.A.dylib                   0x00007fff6f97703c objc_exception_throw + 369 10  com.apple.CoreFoundation          0x00007fff438fdc8d -[NSObject(NSObject) doesNotRecognizeSelector:] + 132 11  com.apple.CoreFoundation          0x00007fff438215de ___forwarding___ + 1468 12  com.apple.CoreFoundation          0x00007fff43820f98 _CF_forwarding_prep_0 + 120 13  lazarus.freepascal.ide            0x000000010030fbcf COCOAWSCOMCTRLS$_$TCOCOAWSCUSTOMPAGE_$__$$_CREATEHANDLE$TWINCONTROL$TCREATEPARAMS$$TLCLINTFHANDLE + 143 (cocoawscomctrls.pas:464) 14  lazarus.freepascal.ide            0x0000000100236f1a CONTROLS$_$TWINCONTROL_$__$$_CREATEWND + 2194 (wincontrol.inc:7551) 15  lazarus.freepascal.ide            0x0000000100236686 CONTROLS$_$TWINCONTROL_$__$$_CREATEHANDLE + 46 (wincontrol.inc:7462) 16  lazarus.freepascal.ide            0x0000000100237d7f CONTROLS$_$TWINCONTROL_$__$$_HANDLENEEDED + 119 (wincontrol.inc:7916) 17  lazarus.freepascal.ide            0x0000000100237d61 CONTROLS$_$TWINCONTROL_$__$$_HANDLENEEDED + 89 (wincontrol.inc:7910) 18  lazarus.freepascal.ide            0x0000000100237d61 CONTROLS$_$TWINCONTROL_$__$$_HANDLENEEDED + 89 (wincontrol.inc:7910) 19  lazarus.freepascal.ide            0x0000000100237d61 CONTROLS$_$TWINCONTROL_$__$$_HANDLENEEDED + 89 (wincontrol.inc:7910) 20  lazarus.freepascal.ide            0x0000000100236d11 CONTROLS$_$TWINCONTROL_$__$$_CREATEWND + 1673 (wincontrol.inc:7531) 21  lazarus.freepascal.ide            0x0000000100656061 ETMESSAGEFRAME$_$TMESSAGESCTRL_$__$$_CREATEWND + 25 (etmessageframe.pas:1730) 22  lazarus.freepascal.ide            0x0000000100236686 CONTROLS$_$TWINCONTROL_$__$$_CREATEHANDLE + 46 (wincontrol.inc:7462) 23  lazarus.freepascal.ide            0x00000001002301fc CONTROLS$_$TWINCONTROL_$__$$_UPDATESHOWING + 84 (wincontrol.inc:4404) 24  lazarus.freepascal.ide            0x000000010022e914 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 212 (wincontrol.inc:3513) 25  lazarus.freepascal.ide            0x000000010022e8d6 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 (wincontrol.inc:3507) 26  lazarus.freepascal.ide            0x000000010022e8d6 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 (wincontrol.inc:3507) 27  lazarus.freepascal.ide            0x000000010022e8d6 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 (wincontrol.inc:3507) 28  lazarus.freepascal.ide            0x000000010022e8d6 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 (wincontrol.inc:3507) 29  lazarus.freepascal.ide            0x000000010022e8d6 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 (wincontrol.inc:3507) 30  lazarus.freepascal.ide            0x000000010022e8d6 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 (wincontrol.inc:3507) 31  lazarus.freepascal.ide            0x000000010022e8d6 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 (wincontrol.inc:3507) 32  lazarus.freepascal.ide            0x000000010022e8d6 CONTROLS$_$TWINCONTROL_$_DOALLAUTOSIZE_$$_UPDATESHOWINGRECURSIVE$TWINCONTROL$BOOLEAN + 150 (wincontrol.inc:3507) 33  lazarus.freepascal.ide            0x000000010022e70c CONTROLS$_$TWINCONTROL_$__$$_DOALLAUTOSIZE + 380 34  lazarus.freepascal.ide            0x0000000100248071 CONTROLS$_$TCONTROL_$__$$_ENABLEAUTOSIZING + 233 35  lazarus.freepascal.ide            0x0000000100c6f02f ANCHORDOCKING$_$TANCHORDOCKMASTER_$__$$_ENABLEALLAUTOSIZING + 87 (anchordocking.pas:2265) 36  lazarus.freepascal.ide            0x0000000100c6f59c ANCHORDOCKING$_$TANCHORDOCKMASTER_$__$$_FULLRESTORELAYOUT$TANCHORDOCKLAYOUTTREE$BOOLEAN$$BOOLEAN + 396 37  lazarus.freepascal.ide            0x0000000100c8ee21 ANCHORDESKTOPOPTIONS$_$TANCHORDESKTOPOPT_$__$$_RESTOREDESKTOP$$BOOLEAN + 41 (anchordesktopoptions.pas:299) 38  lazarus.freepascal.ide            0x00000001006e45c5 ENVIRONMENTOPTS$_$TDESKTOPOPT_$__$$_RESTOREDESKTOP + 69 (environmentopts.pp:1519) 39  lazarus.freepascal.ide            0x000000010007d42c MAIN$_$TMAINIDE_$__$$_RESTOREIDEWINDOWS + 52 (main.pp:2465) 40  lazarus.freepascal.ide            0x0000000100079321 MAIN$_$TMAINIDE_$__$$_STARTIDE + 409 (main.pp:1619) 41  lazarus.freepascal.ide            0x000000010000171e PASCALMAIN + 534 42  lazarus.freepascal.ide            0x0000000100021259 FPC_SYSTEMMAIN + 41 Thread 1: 0   libsystem_pthread.dylib           0x00007fff70c2f428 start_wqthread + 0 1   ???                               0x0000000054485244 0 + 1414025796 Thread 2: 0   libsystem_pthread.dylib           0x00007fff70c2f428 start_wqthread + 0 1   ???                               0x0000000054485244 0 + 1414025796 Thread 3: 0   libsystem_pthread.dylib           0x00007fff70c2f428 start_wqthread + 0 1   ???                               0x0000000054485244 0 + 1414025796 Thread 4: 0   libsystem_pthread.dylib           0x00007fff70c2f428 start_wqthread + 0 1   ???                               0x0000600003508160 0 + 105553171874144 Thread 5: 0   libsystem_pthread.dylib           0x00007fff70c2f428 start_wqthread + 0 Thread 6: 0   libsystem_pthread.dylib           0x00007fff70c2f428 start_wqthread + 0 1   ???                               0x0000000054485244 0 + 1414025796 Thread 7: 0   libsystem_pthread.dylib           0x00007fff70c2f428 start_wqthread + 0 1   ???                               0x0000000000001303 0 + 4867 Thread 0 crashed with X86 Thread State (64-bit):   rax: 0x0000000000000000  rbx: 0x00000001060335c0  rcx: 0x00007ffeefbfd588  rdx: 0x0000000000000000   rdi: 0x0000000000000307  rsi: 0x0000000000000006  rbp: 0x00007ffeefbfd5c0  rsp: 0x00007ffeefbfd588    r8: 0x00007ffeefbfd448   r9: 0x00007ffeefbfd620  r10: 0x0000000000000000  r11: 0x0000000000000206   r12: 0x0000000000000307  r13: 0x0000003000000008  r14: 0x0000000000000006  r15: 0x000000000000002d   rip: 0x00007fff70b7cb86  rfl: 0x0000000000000206  cr2: 0x00007fffa35bd188 Logical CPU:     0 Error Code:      0x02000148 Trap Number:     133 Binary Images:        0x100000000 -        0x100e97ff7 +lazarus.freepascal.ide (2.1.0 - 1) <237F11E6-BD88-32A6-A35D-0AC745015691> /usr/local/share/lazarus/lazarus.app/Contents/MacOS/lazarus        0x105f07000 -        0x105f0a047  libobjc-trampolines.dylib (750.1) <9038F299-E122-39D1-BBB9-48EC919CD5CE> /usr/lib/libobjc-trampolines.dylib        0x105f7d000 -        0x105ffb6a7  dyld (635.2) <1780094A-8FE2-3EAA-B4A3-C4CF14BC5196> /usr/lib/dyld     0x7fff3b73e000 -     0x7fff3b7b8fff com.apple.driver.AppleIntelHD4000GraphicsMTLDriver (12.2.17 - 12.0.2) <28ACDEB1-84AA-30A3-A21D-7DA62D7E7472> /System/Library/Extensions/AppleIntelHD4000GraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelHD4000GraphicsMTLDriver     0x7fff3f34f000 -     0x7fff3f4f5ff7 com.apple.GeForceMTLDriver (12.0.19 - 12.0.0) <05A39D8A-760C-329B-B55B-362D297F5ED7> /System/Library/Extensions/GeForceMTLDriver.bundle/Contents/MacOS/GeForceMTLDriver     0x7fff3f8c7000 -     0x7fff3f8c7fff  com.apple.Accelerate (1.11 - Accelerate 1.11) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate     0x7fff3f8c8000 -     0x7fff3f8deff7  libCGInterfaces.dylib (506.19.1) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib     0x7fff3f8df000 -     0x7fff401d3fcf  com.apple.vImage (8.1 - ???) <57E602AE-8EA5-337C-9ECF-0A9696B6CCA9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage     0x7fff401d4000 -     0x7fff4037ffcf  libBLAS.dylib (1243.200.4) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib     0x7fff40380000 -     0x7fff403c5fff  libBNNS.dylib (38.200.5) <71968F7E-1679-314D-A7FE-C904B3165AB4> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib     0x7fff403c6000 -     0x7fff4077ffff  libLAPACK.dylib (1243.200.4) <670B40E4-AE2F-3311-8ACC-E355F9A36769> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib     0x7fff40780000 -     0x7fff40795ffb  libLinearAlgebra.dylib (1243.200.4) <38A569CB-514E-3376-AE9D-38CBD79DC49E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib     0x7fff40796000 -     0x7fff4079bff3  libQuadrature.dylib (3.200.2) <6FFAC142-415D-3AF0-BC09-336302F11934> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib     0x7fff4079c000 -     0x7fff40819ffb  libSparse.dylib (79.200.5) <0D7E71A4-10D2-3979-B386-D2426ADAF6D7> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib     0x7fff4081a000 -     0x7fff4082cffb  libSparseBLAS.dylib (1243.200.4) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib     0x7fff4082d000 -     0x7fff409cbfdb  libvDSP.dylib (671.220.1) <95AA3236-5D63-35AF-9305-FDC361365110> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib     0x7fff409cc000 -     0x7fff40b43ff3  libvMisc.dylib (671.220.1) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib     0x7fff40b44000 -     0x7fff40b44fff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <0AB4E69A-8159-3BA5-984D-002B5ACB175C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib     0x7fff40cf5000 -     0x7fff41b15ff3  com.apple.AppKit (6.9 - 1671.10.106) <179A5F4A-6467-31BD-93F2-CC27E046221E> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit     0x7fff41b67000 -     0x7fff41b67fff com.apple.ApplicationServices (50.1 - 50.1) <470C0943-30AD-3BA2-AFCE-EB7DD26E1709> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices     0x7fff41b68000 -     0x7fff41bd3ff7 com.apple.ApplicationServices.ATS (377 - 453.11) <7599E619-EE21-3EB7-875B-AE3B8D3E13BB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS     0x7fff41c6c000 -     0x7fff41d8bfff  libFontParser.dylib (228.6) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib     0x7fff41d8c000 -     0x7fff41dd7fff  libFontRegistry.dylib (228.12) <480D472D-C8FB-321D-86EC-2EA6927A97AD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib     0x7fff41e36000 -     0x7fff41e69ff7  libTrueTypeScaler.dylib (228.6) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib     0x7fff41ed3000 -     0x7fff41ed7ff3  com.apple.ColorSyncLegacy (4.13.0 - 1) <90641B6B-D07B-3577-B594-965825544B60> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy     0x7fff41f74000 -     0x7fff41fc6ff3  com.apple.HIServices (1.22 - 627.14.2) <01F309D6-32E7-3C4F-A38B-8206EE3076CC> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices     0x7fff41fc7000 -     0x7fff41fd5ff3  com.apple.LangAnalysis (1.7.0 - 1.7.0) <67BC5855-B7A3-39E6-B5DD-52B287EB1532> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis     0x7fff41fd6000 -     0x7fff42022fff com.apple.print.framework.PrintCore (14.0 - 503.7) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore     0x7fff42023000 -     0x7fff4205eff7  com.apple.QD (3.12 - 407.2) <94A30038-C545-327A-B1C0-E19C79D62BAB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD     0x7fff4205f000 -     0x7fff4206bff7 com.apple.speech.synthesis.framework (8.1.0 - 8.1.0) <823830AC-62A6-36CC-A659-6BC10F2AC6F5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis     0x7fff4206c000 -     0x7fff42308ff7 com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox     0x7fff4230a000 -     0x7fff4230afff com.apple.audio.units.AudioUnit (1.14 - 1.14) /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit     0x7fff4266e000 -     0x7fff42a2fff7  com.apple.CFNetwork (975.0.3 - 975.0.3) <99BD4FA0-8BD3-35E5-8FB1-C757D439716C> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork     0x7fff42a49000 -     0x7fff42d50ff7  com.apple.HIToolbox (2.1.1 - 917.2) <0B91F11C-0895-3A7B-9A3B-2B6B1267EA1A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox     0x7fff42d5b000 -     0x7fff42defff3  com.apple.ink.framework (10.9 - 225) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink     0x7fff42e30000 -     0x7fff42e36ff7 com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <1C38B9CB-DD45-3A7B-9D4C-631855A4EE32> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition     0x7fff42f5d000 -     0x7fff42f5dfff  com.apple.Cocoa (6.11 - 23) <4D5D4968-E233-3598-B434-E1009D48A628> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa     0x7fff42f6b000 -     0x7fff43037fff  com.apple.ColorSync (4.13.0 - 3340) <0618DA46-5A5E-339D-BB2F-ED66A2BFCCF9> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync     0x7fff431d2000 -     0x7fff43262fff  com.apple.audio.CoreAudio (4.3.0 - 4.3.0) /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio     0x7fff432c8000 -     0x7fff432f3ff7  com.apple.CoreBluetooth (1.0 - 1) <61235BEA-BF5F-31B2-B9C1-DE722E15840F> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth     0x7fff432f4000 -     0x7fff436a2fff  com.apple.CoreData (120 - 866.1) <2554E8DD-7E40-3763-A528-3BC3666AFC09> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData     0x7fff436a3000 -     0x7fff4378cff7  com.apple.CoreDisplay (101.3 - 104.4) <52C96B6A-B119-3BE2-B47D-65F12E987609> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay     0x7fff4378d000 -     0x7fff43bdbff7  com.apple.CoreFoundation (6.9 - 1560.12) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation     0x7fff43bdd000 -     0x7fff44287ff7  com.apple.CoreGraphics (2.0 - 1247.4.1) <57F76BD4-4472-3B04-A41B-87767D5639CD> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics     0x7fff44289000 -     0x7fff445b2fff  com.apple.CoreImage (14.1.0 - 710.2.240) /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage     0x7fff44a68000 -     0x7fff44a68fff  com.apple.CoreServices (934 - 934) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices     0x7fff44a69000 -     0x7fff44ae7ffb  com.apple.AE (771 - 771) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE     0x7fff44ae8000 -     0x7fff44dc0ff7 com.apple.CoreServices.CarbonCore (1178.11 - 1178.11) <9FBE7BFB-3A81-37AC-8E15-E6F7932BBDC0> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore     0x7fff44dc1000 -     0x7fff44e0bff7 com.apple.DictionaryServices (1.2 - 284.16.3) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices     0x7fff44e0c000 -     0x7fff44e14ffb com.apple.CoreServices.FSEvents (1239.200.12 - 1239.200.12) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents     0x7fff44e15000 -     0x7fff44fe0fff  com.apple.LaunchServices (934 - 934) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices     0x7fff44fe1000 -     0x7fff45083fff  com.apple.Metadata (10.7.0 - 1191.52) <5A758D93-4BBD-3C6D-861B-000536ED9B2D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata     0x7fff45084000 -     0x7fff450cfff7 com.apple.CoreServices.OSServices (934 - 934) <1D2AC09A-653F-3C2D-B5B9-F9ABA307E51C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices     0x7fff450d0000 -     0x7fff4513eff7  com.apple.SearchKit (1.4.0 - 1.4.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit     0x7fff4513f000 -     0x7fff45163ffb com.apple.coreservices.SharedFileList (71.27 - 71.27) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList     0x7fff454ab000 -     0x7fff45610ffb  com.apple.CoreText (352.0 - 584.25) /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText     0x7fff45611000 -     0x7fff4564efff  com.apple.CoreVideo (1.8 - 0.0) /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo     0x7fff4564f000 -     0x7fff456e5ffb com.apple.framework.CoreWLAN (13.0 - 1370.8) <735EEBA3-C63B-38C8-A1A7-23B12C2E9550> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN     0x7fff45962000 -     0x7fff45967fff  com.apple.DiskArbitration (2.7 - 2.7) /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration     0x7fff45b30000 -     0x7fff45efefff  com.apple.Foundation (6.9 - 1560.12) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation     0x7fff45f6f000 -     0x7fff45f9fff3  com.apple.GSS (4.0 - 2.0) <721B6FEF-9E0E-311B-8CAF-93ADEE2AE548> /System/Library/Frameworks/GSS.framework/Versions/A/GSS     0x7fff460b9000 -     0x7fff461c3ff3  com.apple.Bluetooth (6.0.9 - 6.0.9f2) <0EDECAF3-FF86-3F7D-B916-2D7E67FF67AE> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth     0x7fff46225000 -     0x7fff462b7ff7  com.apple.framework.IOKit (2.0.2 - 1483.220.15) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit     0x7fff462b9000 -     0x7fff462c3ff7  com.apple.IOSurface (255.1 - 255.1) <538F0257-A408-36AF-AB1E-1D7037D6359E> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface     0x7fff4631a000 -     0x7fff464bbff7 com.apple.ImageIO.framework (3.3.0 - 1821.6.4.1) /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO     0x7fff464bc000 -     0x7fff464c0ffb  libGIF.dylib (1821.6.4.1) <658AC780-4640-3A69-8629-61F60C656687> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib     0x7fff464c1000 -     0x7fff465a6fff  libJP2.dylib (1821.6.4.1) /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib     0x7fff465a7000 -     0x7fff465ccffb  libJPEG.dylib (1821.6.4.1) <8863EEE3-14A1-3F15-82BD-BED2539D28C5> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib     0x7fff468a0000 -     0x7fff468c6ff3  libPng.dylib (1821.6.4.1) /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib     0x7fff468c7000 -     0x7fff468c9ff7  libRadiance.dylib (1821.6.4.1) <7F9FB9C1-296E-30C3-AB0B-91FEE157332A> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib     0x7fff468ca000 -     0x7fff46917fff  libTIFF.dylib (1821.6.4.1) <6F844D7A-8508-3765-BE85-58C55396E37E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib     0x7fff479b4000 -     0x7fff479cdfff  com.apple.Kerberos (3.0 - 1) <8BE3D524-257D-3663-A937-F1AC76BDF4D9> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos     0x7fff483ee000 -     0x7fff48481fff  com.apple.Metal (157.60 - 157.60) /System/Library/Frameworks/Metal.framework/Versions/A/Metal     0x7fff4849e000 -     0x7fff484beff7 com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore     0x7fff484bf000 -     0x7fff4853dff7 com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <80DE2FD1-85DB-3E98-98BD-F22A2600DD25> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage     0x7fff4853e000 -     0x7fff48566fff com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <49039DEE-D0EC-33FF-BE10-997A520D2E38> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix     0x7fff48567000 -     0x7fff48699ff7 com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <425D1FA4-17A3-3D00-8BE4-7A682FF279B5> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork     0x7fff4869a000 -     0x7fff486b5ff7 com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector     0x7fff486b6000 -     0x7fff486b6ff7 com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <3910EC50-5B16-3695-B867-741E3B54FA8B> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders     0x7fff498b5000 -     0x7fff498c1ffb  com.apple.NetFS (6.0 - 4.0) <529E29A9-5E77-3A8C-A982-CF55F949FE5D> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS     0x7fff4c381000 -     0x7fff4c3d9ff7  com.apple.opencl (2.12.7 - 2.12.7) /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL     0x7fff4c3da000 -     0x7fff4c3f6ff7  com.apple.CFOpenDirectory (10.14 - 207.200.4) <7E4EFF02-2596-31E6-88DE-29C89E2837E4> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory     0x7fff4c3f7000 -     0x7fff4c403ffb  com.apple.OpenDirectory (10.14 - 207.200.4) <52A3918E-0F7A-33FD-87EE-21A37B37D13B> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory     0x7fff4cd66000 -     0x7fff4cd68fff libCVMSPluginSupport.dylib (17.0.37) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib     0x7fff4cd69000 -     0x7fff4cd6eff3  libCoreFSCache.dylib (163.20) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib     0x7fff4cd6f000 -     0x7fff4cd73fff  libCoreVMClient.dylib (163.20) <45A2C724-F3D1-316A-9A41-CAB8E2A390EC> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib     0x7fff4cd74000 -     0x7fff4cd7cffb  libGFXShared.dylib (17.0.37) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib     0x7fff4cd7d000 -     0x7fff4cd88fff  libGL.dylib (17.0.37) <8DCB2714-ECB1-39EC-931D-C58D9E91B51C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib     0x7fff4cd89000 -     0x7fff4cdc3fef  libGLImage.dylib (17.0.37) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib     0x7fff4cf37000 -     0x7fff4cf74fff  libGLU.dylib (17.0.37) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib     0x7fff4d924000 -     0x7fff4d933ff3  com.apple.opengl (17.0.37 - 17.0.37) <6BCCA53E-5621-32ED-BA9A-38B1C2499ED5> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL     0x7fff4e78f000 -     0x7fff4e9e7fff  com.apple.QuartzCore (1.11 - 694.22.4.1) <1F5A49A9-370C-311B-B67C-DEA6DF6D2983> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore     0x7fff4f235000 -     0x7fff4f55bff7  com.apple.security (7.0 - 58286.220.15) <6725D63D-378F-3751-8602-3122016E4AA4> /System/Library/Frameworks/Security.framework/Versions/A/Security     0x7fff4f55c000 -     0x7fff4f5ebfff com.apple.securityfoundation (6.0 - 55185.200.14) <236BACD7-163F-3F35-B710-2C62988AA251> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation     0x7fff4f61d000 -     0x7fff4f621ff3 com.apple.xpc.ServiceManagement (1.0 - 1) /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement     0x7fff4f9de000 -     0x7fff4fa4eff3 com.apple.SystemConfiguration (1.17 - 1.17) /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration     0x7fff52cb5000 -     0x7fff52d5afe7  com.apple.APFS (1.0 - 1) /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS     0x7fff537a4000 -     0x7fff537a5ff3 com.apple.AggregateDictionary (1.0 - 1) <1DEBBE36-8945-3AD8-BD48-2850AD845711> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary     0x7fff53da1000 -     0x7fff53dcdff7 com.apple.framework.Apple80211 (13.0 - 1376.2) <821DE2A3-1CAD-3A7D-A2DD-41EBA3A6FEF3> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211     0x7fff540a9000 -     0x7fff540b8fcf com.apple.AppleFSCompression (96.200.3 - 1.0) /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression     0x7fff541b6000 -     0x7fff541c1fff com.apple.AppleIDAuthSupport (1.0 - 1) <5362D9AD-A2AE-3436-97CE-C353124504E5> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport     0x7fff54202000 -     0x7fff5424bff3  com.apple.AppleJPEG (1.0 - 1) <9A690E6E-F987-3660-BED6-B1A4D1906B6C> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG     0x7fff5449d000 -     0x7fff544c5ff7  com.apple.applesauce (1.0 - ???) <60BB16D6-DE7E-356A-B9DE-F73EE179934A> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce     0x7fff5462b000 -     0x7fff54641ffb com.apple.AssertionServices (1.0 - 1) <8FB0D908-6C46-3399-92D6-4E7D4B5F4F19> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices     0x7fff5497d000 -     0x7fff54c20ffb  com.apple.AuthKit (1.0 - 1) <8920796A-C818-3163-B6D0-FD05D1A6ADF5> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit     0x7fff54df1000 -     0x7fff54dfaff3 com.apple.coreservices.BackgroundTaskManagement (1.0 - 57.1) <972F41B3-7DF7-3BF1-ACCA-A093A4328ADF> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement     0x7fff54dfb000 -     0x7fff54e9dff7 com.apple.backup.framework (1.10 - ???) <46534B04-DD0E-357B-9CB5-F88AAC6AF4ED> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup     0x7fff54e9e000 -     0x7fff54f0fffb  com.apple.BaseBoard (360.24 - 360.24) /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard     0x7fff56ac0000 -     0x7fff56ac9fff  com.apple.CommonAuth (4.0 - 2.0) <93CF1D80-A3A8-378B-9DF7-BF17A206C57D> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth     0x7fff577db000 -     0x7fff577effff  com.apple.CoreEmoji (1.0 - 69.19.8) /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji     0x7fff57dc5000 -     0x7fff57e37ff7  com.apple.CoreNLP (1.0 - 130.15.22) <401F5284-A984-32A1-A547-CC8156381070> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP     0x7fff580f2000 -     0x7fff580faffb com.apple.CorePhoneNumbers (1.0 - 1) /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers     0x7fff58289000 -     0x7fff582bafff com.apple.CoreServicesInternal (357 - 357) <2D012EB3-83BF-3E51-A2BE-41AF26F2DDF0> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal     0x7fff58684000 -     0x7fff58712ff7 com.apple.CoreSymbolication (10.1 - 64460.6) /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication     0x7fff587a2000 -     0x7fff588cefff  com.apple.coreui (2.1 - 498.46) <7637C723-B16D-3001-B3AC-0612349D1CC5> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI     0x7fff588cf000 -     0x7fff58a54fff  com.apple.CoreUtils (5.7.4 - 574.17) /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils     0x7fff58aab000 -     0x7fff58b0effb com.apple.framework.CoreWiFi (13.0 - 1370.8) /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi     0x7fff58b0f000 -     0x7fff58b20ffb com.apple.CrashReporterSupport (10.13 - 938.23) <36754BB2-680F-36AE-A5DE-548B4F41F0AE> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport     0x7fff58ba3000 -     0x7fff58bb2ff3 com.apple.framework.DFRFoundation (1.0 - 211) /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation     0x7fff58bb3000 -     0x7fff58bb7ff7 com.apple.DSExternalDisplay (3.1 - 380) /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay     0x7fff58c3a000 -     0x7fff58cb1ffb com.apple.datadetectorscore (7.0 - 590.24) <1C9AC888-8B75-3CF3-AD70-42D40C435E67> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore     0x7fff58cff000 -     0x7fff58d40fff  com.apple.DebugSymbols (185 - 185) <12419E0F-BC7A-3F3A-AA53-5F068DAED725> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols     0x7fff58d41000 -     0x7fff58e9aff7  com.apple.desktopservices (1.13.1 - ???) /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv     0x7fff59ee2000 -     0x7fff5a30afff  com.apple.vision.FaceCore (3.3.4 - 3.3.4) /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore     0x7fff5dc2c000 -     0x7fff5dc2dfff  libmetal_timestamp.dylib (902.1.60) <16F3973E-20CB-3FFA-9C8B-A2287AF03AA0> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3902/Libraries/libmetal_timestamp.dylib     0x7fff5f2d2000 -     0x7fff5f2d7ff7  com.apple.GPUWrangler (3.25.6 - 3.25.6) /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler     0x7fff6013d000 -     0x7fff6014cfff  com.apple.GraphVisualizer (1.0 - 5) /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer     0x7fff6029d000 -     0x7fff60312fff  com.apple.Heimdal (4.0 - 2.0) /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal     0x7fff616fe000 -     0x7fff61705ffb  com.apple.IOAccelerator (400.27 - 400.27) <6FA8A133-57A7-3C35-BF94-8469B09885FB> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator     0x7fff61709000 -     0x7fff61722fff  com.apple.IOPresentment (1.0 - 42.6) /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment     0x7fff61b37000 -     0x7fff61b66ff7  com.apple.IconServices (379 - 379) <0A25D75C-35A7-3ED5-8900-EBC05522B5A9> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices     0x7fff61e05000 -     0x7fff61e18fff com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <1DB4E862-C010-38BA-B535-5DAD679FEADA> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle     0x7fff61e33000 -     0x7fff61f2afff com.apple.LanguageModeling (1.0 - 159.15.15) /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling     0x7fff61f2b000 -     0x7fff61f6cff7 com.apple.Lexicon-framework (1.0 - 33.15.10) <90C1CFE1-9935-3F4F-8A9B-1DD697F2FF3D> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon     0x7fff61f73000 -     0x7fff61f79ff7  com.apple.LinguisticData (1.0 - 238.15.29) /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData     0x7fff62cd5000 -     0x7fff62cfdffb com.apple.spotlight.metadata.utilities (1.0 - 1191.52) <38A9B11A-9D5C-3CCA-A163-EC17242FDC68> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities     0x7fff62cfe000 -     0x7fff62d90fff com.apple.gpusw.MetalTools (1.0 - 1) <5B86F005-D12D-3B0B-8906-808926D3DA12> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools     0x7fff62f3a000 -     0x7fff62f55ff3  com.apple.MobileKeyBag (2.0 - 1.0) <6E36F030-D7E8-341D-A493-414F5E13B1E9> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag     0x7fff62fe3000 -     0x7fff6300dff7 com.apple.MultitouchSupport.framework (2410.5 - 2410.5) <8D87A3ED-4CBD-300F-92E3-B1B79D7E0BF3> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport     0x7fff63280000 -     0x7fff6328afff  com.apple.NetAuth (6.2 - 6.2) <55DC741A-A01A-380C-B2D3-244241DA1F2C> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth     0x7fff63b56000 -     0x7fff63bacfff  com.apple.OTSVG (1.0 - ???) <5F2E7A0E-384E-3545-A9D5-EC4406E92AF4> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG     0x7fff64d12000 -     0x7fff64d21ff3 com.apple.PerformanceAnalysis (1.217 - 217) <8560F263-31F4-3CCA-84B1-30C296DC1A7D> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis     0x7fff66ce1000 -     0x7fff66cffff7  com.apple.ProtocolBuffer (1 - 263) /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer     0x7fff66eae000 -     0x7fff66f06f0f  com.apple.ROCKit (24 - 24) <5437F6F7-453F-3D75-9E87-D2A090D82D25> /System/Library/PrivateFrameworks/ROCKit.framework/Versions/A/ROCKit     0x7fff67021000 -     0x7fff67044ffb com.apple.RemoteViewServices (2.0 - 128) <68530B4D-B2C0-3271-941B-D9EA62095727> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices     0x7fff689b4000 -     0x7fff68ad2fff  com.apple.Sharing (1214.9 - 1214.9) <2A377CA5-C66F-3913-8401-951A3AE4D299> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing     0x7fff69885000 -     0x7fff69b36ff3  com.apple.SkyLight (1.600.0 - 336.81.5) /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight     0x7fff6a306000 -     0x7fff6a313fff com.apple.SpeechRecognitionCore (5.0.21 - 5.0.21) <816EC315-3E76-37B7-A495-B4AE031DA439> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore     0x7fff6b173000 -     0x7fff6b200ff7  com.apple.Symbolication (10.1 - 64460.8) <1B488612-4C7F-3D9D-B6DC-64CF8D2CB3D6> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication     0x7fff6b709000 -     0x7fff6b716ffb  com.apple.TCC (1.0 - 1) /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC     0x7fff6b988000 -     0x7fff6ba4fff7  com.apple.TextureIO (3.8.4 - 3.8.1) /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO     0x7fff6bb10000 -     0x7fff6bccafff  com.apple.UIFoundation (1.0 - 551) <7B73C4E0-256B-3C59-8E18-475A42BE0B12> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation     0x7fff6c9b9000 -     0x7fff6caa2ff7  com.apple.ViewBridge (401.1 - 401.1) /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge     0x7fff6d2c2000 -     0x7fff6d2c5fff com.apple.dt.XCTTargetBootstrap (1.0 - 1) <697834E4-FEFD-305C-80EE-5052E61573FA> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap     0x7fff6d6f6000 -     0x7fff6d6f8ff3  com.apple.loginsupport (1.0 - 1) <5F1E000D-0674-3413-AB3E-83F7974666FB> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport     0x7fff6d9b2000 -     0x7fff6d9eafff  libCRFSuite.dylib (41.15.4) <62EDD39F-6D1B-334B-A9A2-5800714255BB> /usr/lib/libCRFSuite.dylib     0x7fff6d9ed000 -     0x7fff6d9f8ff7  libChineseTokenizer.dylib (28.15.3) <8CD1C213-7F62-3F02-BFB1-D0A5EFF92AB0> /usr/lib/libChineseTokenizer.dylib     0x7fff6da89000 -     0x7fff6da8aff7 libDiagnosticMessagesClient.dylib (107) /usr/lib/libDiagnosticMessagesClient.dylib     0x7fff6dac1000 -     0x7fff6dc84ff7  libFosl_dynamic.dylib (18.3.2) <6EF1CB2A-2BDA-3458-B631-F794D72660FD> /usr/lib/libFosl_dynamic.dylib     0x7fff6dcda000 -     0x7fff6dcf9fff  libMobileGestalt.dylib (645.220.9) /usr/lib/libMobileGestalt.dylib     0x7fff6dcfa000 -     0x7fff6dcfafff libOpenScriptingUtil.dylib (179) <0664670D-C7E1-3D27-814B-B9C445AAF0DC> /usr/lib/libOpenScriptingUtil.dylib     0x7fff6de3b000 -     0x7fff6de3cffb  libSystem.B.dylib (1252.200.5) /usr/lib/libSystem.B.dylib     0x7fff6dec6000 -     0x7fff6dec7fff  libThaiTokenizer.dylib (2.15.1) /usr/lib/libThaiTokenizer.dylib     0x7fff6deda000 -     0x7fff6def0ffb  libapple_nghttp2.dylib (1.24.1) /usr/lib/libapple_nghttp2.dylib     0x7fff6def1000 -     0x7fff6df1affb  libarchive.2.dylib (54.200.3) /usr/lib/libarchive.2.dylib     0x7fff6df1b000 -     0x7fff6e01aff7  libate.dylib (1.13.8) <0B27DB67-00B9-3979-9307-447C593A4AEB> /usr/lib/libate.dylib     0x7fff6e01e000 -     0x7fff6e01eff3  libauto.dylib (187) <01824E49-F2EF-3FC1-ABF3-782EFDF6CA17> /usr/lib/libauto.dylib     0x7fff6e0f5000 -     0x7fff6e105ff3  libbsm.0.dylib (39.200.18) <5E5098D0-F7B2-32A1-8038-E709F6718D4E> /usr/lib/libbsm.0.dylib     0x7fff6e106000 -     0x7fff6e114fff  libbz2.1.0.dylib (38.200.3) <4EE3C5E8-BEF3-3910-A231-B1AE2B437E01> /usr/lib/libbz2.1.0.dylib     0x7fff6e115000 -     0x7fff6e16cff7  libc++.1.dylib (400.9.4) /usr/lib/libc++.1.dylib     0x7fff6e16d000 -     0x7fff6e182fff  libc++abi.dylib (400.17) /usr/lib/libc++abi.dylib     0x7fff6e183000 -     0x7fff6e183ff3  libcharset.1.dylib (51.200.6) /usr/lib/libcharset.1.dylib     0x7fff6e184000 -     0x7fff6e194ffb  libcmph.dylib (6.15.1) <5D776FF6-DF7F-3EDD-B920-C07ED76C672B> /usr/lib/libcmph.dylib     0x7fff6e195000 -     0x7fff6e1adfdb  libcompression.dylib (52.200.13) <13B000B6-285E-3A31-A4AD-6EA2742351F6> /usr/lib/libcompression.dylib     0x7fff6e458000 -     0x7fff6e46efff  libcoretls.dylib (155.220.1) <3F98C144-397C-36A2-84F1-BB0D841D3D89> /usr/lib/libcoretls.dylib     0x7fff6e46f000 -     0x7fff6e470ff3 libcoretls_cfhelpers.dylib (155.220.1) <0C190169-8EB8-3BA2-89BB-60265BB502F9> /usr/lib/libcoretls_cfhelpers.dylib     0x7fff6eae7000 -     0x7fff6eb3dffb  libcups.2.dylib (462.9) <51E06E95-891F-3B88-A8C3-35B514C57239> /usr/lib/libcups.2.dylib     0x7fff6ec75000 -     0x7fff6ec75fff  libenergytrace.dylib (17.200.1) /usr/lib/libenergytrace.dylib     0x7fff6eca7000 -     0x7fff6ecacff7  libgermantok.dylib (17.15.2) <9CBF0658-E83B-32E6-B674-3EE72D22C041> /usr/lib/libgermantok.dylib     0x7fff6ecad000 -     0x7fff6ecb2ff7  libheimdal-asn1.dylib (520.220.2) <5302394C-ECF0-3C3B-BA67-4830EEF3CC40> /usr/lib/libheimdal-asn1.dylib     0x7fff6ecde000 -     0x7fff6edcfff7  libiconv.2.dylib (51.200.6) <3240A278-F537-3EC8-BE0C-983797520A50> /usr/lib/libiconv.2.dylib     0x7fff6edd0000 -     0x7fff6f033ffb  libicucore.A.dylib (62108.0.1) <969815D4-A345-31BB-82B7-0C3B58CA7E90> /usr/lib/libicucore.A.dylib     0x7fff6f080000 -     0x7fff6f081fff  liblangid.dylib (128.15.1) /usr/lib/liblangid.dylib     0x7fff6f082000 -     0x7fff6f09afff  liblzma.5.dylib (10.200.3) <3ADDFA63-F37A-3C9C-91E4-58EE3113B9A1> /usr/lib/liblzma.5.dylib     0x7fff6f0b2000 -     0x7fff6f162fff  libmecab.1.0.0.dylib (779.19.2) <314FE1B9-3B4E-3B89-A101-33CE7B78FCE6> /usr/lib/libmecab.1.0.0.dylib     0x7fff6f163000 -     0x7fff6f3a0fff  libmecabra.dylib (779.19.2) <0ECEC3FC-935D-3EA5-8B3D-5CBD4E80AB78> /usr/lib/libmecabra.dylib     0x7fff6f578000 -     0x7fff6f8d0fff  libnetwork.dylib (1229.221.1) /usr/lib/libnetwork.dylib     0x7fff6f961000 -     0x7fff700eafd7  libobjc.A.dylib (750.1) <8CD466AD-D084-35D4-8760-59180F0220BF> /usr/lib/libobjc.A.dylib     0x7fff700fd000 -     0x7fff70101ffb  libpam.2.dylib (22.200.1) <8C419238-675A-3C41-B8D4-95E391CA630F> /usr/lib/libpam.2.dylib     0x7fff70104000 -     0x7fff7013aff7  libpcap.A.dylib (79.200.4) <5939AB23-B2A9-3C03-B6C1-4F0E5A21D9FC> /usr/lib/libpcap.A.dylib     0x7fff70254000 -     0x7fff7026cffb  libresolv.9.dylib (65.200.2) <0FEAEB01-B926-37FA-AB47-99BAC481C10B> /usr/lib/libresolv.9.dylib     0x7fff702c0000 -     0x7fff7048cff7  libsqlite3.dylib (274.20) <92515835-B51A-35DA-98E2-07A63353D4B8> /usr/lib/libsqlite3.dylib     0x7fff70719000 -     0x7fff7071cffb  libutil.dylib (51.200.4) <91EE9BF4-FB06-3260-B502-7EFDAD5AF59B> /usr/lib/libutil.dylib     0x7fff7071d000 -     0x7fff7072afff  libxar.1.dylib (404) <4B4D0206-0B62-3E89-AD07-E7BB9E4DFA68> /usr/lib/libxar.1.dylib     0x7fff7072f000 -     0x7fff70812fff  libxml2.2.dylib (32.8) <1CE77741-2E67-34B6-BB9F-B8E043966FCE> /usr/lib/libxml2.2.dylib     0x7fff70813000 -     0x7fff7083bff3  libxslt.1.dylib (16.1) /usr/lib/libxslt.1.dylib     0x7fff7083c000 -     0x7fff7084effb  libz.1.dylib (70.200.4) <99A3D725-8388-38B4-B66C-5E9006E6F072> /usr/lib/libz.1.dylib     0x7fff708bf000 -     0x7fff708c3ff3  libcache.dylib (81) /usr/lib/system/libcache.dylib     0x7fff708c4000 -     0x7fff708ceff3  libcommonCrypto.dylib (60118.220.1) <1099E427-6E81-3059-87AF-6F5FD81CA998> /usr/lib/system/libcommonCrypto.dylib     0x7fff708cf000 -     0x7fff708d6fff  libcompiler_rt.dylib (63.4) /usr/lib/system/libcompiler_rt.dylib     0x7fff708d7000 -     0x7fff708e0ff3  libcopyfile.dylib (146.200.3) <4BCDADBF-79F5-3829-B47D-64DA0D44BCBF> /usr/lib/system/libcopyfile.dylib     0x7fff708e1000 -     0x7fff70965fdf  libcorecrypto.dylib (602.220.6) /usr/lib/system/libcorecrypto.dylib     0x7fff709ec000 -     0x7fff70a26ff7  libdispatch.dylib (1008.220.2) /usr/lib/system/libdispatch.dylib     0x7fff70a27000 -     0x7fff70a56fff  libdyld.dylib (635.2) <1B79A5CE-125F-301F-A441-C1869573AED0> /usr/lib/system/libdyld.dylib     0x7fff70a57000 -     0x7fff70a57ffb  libkeymgr.dylib (30) /usr/lib/system/libkeymgr.dylib     0x7fff70a58000 -     0x7fff70a64ff7  libkxld.dylib (4903.221.2) <16D75C5C-584A-3848-84C0-3BFB312AEB92> /usr/lib/system/libkxld.dylib     0x7fff70a65000 -     0x7fff70a65ff7  liblaunch.dylib (1336.220.5) <95EB6EAF-2DC5-344F-BADB-CA4E35E4E503> /usr/lib/system/liblaunch.dylib     0x7fff70a66000 -     0x7fff70a6bfff  libmacho.dylib (921) /usr/lib/system/libmacho.dylib     0x7fff70a6c000 -     0x7fff70a6effb  libquarantine.dylib (86.220.1) <6AE5AEEC-A9FD-3CF8-92DD-12B5AFBE12DE> /usr/lib/system/libquarantine.dylib     0x7fff70a6f000 -     0x7fff70a70ff3  libremovefile.dylib (45.200.2) /usr/lib/system/libremovefile.dylib     0x7fff70a71000 -     0x7fff70a88ff3  libsystem_asl.dylib (356.200.4) /usr/lib/system/libsystem_asl.dylib     0x7fff70a89000 -     0x7fff70a89fff  libsystem_blocks.dylib (73) <26419398-C30C-30F1-B656-A92AFA9560F6> /usr/lib/system/libsystem_blocks.dylib     0x7fff70a8a000 -     0x7fff70b12fff  libsystem_c.dylib (1272.200.26) <3DEEE96E-6DF6-35AD-8654-D69AC26B907B> /usr/lib/system/libsystem_c.dylib     0x7fff70b13000 -     0x7fff70b16ff7 libsystem_configuration.dylib (963.200.27) <02CC3996-B34E-333C-8806-AE2699D34424> /usr/lib/system/libsystem_configuration.dylib     0x7fff70b17000 -     0x7fff70b1aff7 libsystem_coreservices.dylib (66) <254B6849-2C8F-302C-8616-B8324A11AB30> /usr/lib/system/libsystem_coreservices.dylib     0x7fff70b1b000 -     0x7fff70b21ffb  libsystem_darwin.dylib (1272.200.26) <974E9EF7-DE72-34B7-B056-0A81C10DF8EB> /usr/lib/system/libsystem_darwin.dylib     0x7fff70b22000 -     0x7fff70b28ff7  libsystem_dnssd.dylib (878.200.35) /usr/lib/system/libsystem_dnssd.dylib     0x7fff70b29000 -     0x7fff70b75ff3  libsystem_info.dylib (517.200.9) <0707C387-D7DE-372E-8FF1-3DE5C91932D6> /usr/lib/system/libsystem_info.dylib     0x7fff70b76000 -     0x7fff70b9dff7  libsystem_kernel.dylib (4903.221.2) <0E882078-7330-3B49-AA5D-3CDB5645A4E5> /usr/lib/system/libsystem_kernel.dylib     0x7fff70b9e000 -     0x7fff70be9ff7  libsystem_m.dylib (3158.200.7) <43D1796B-954F-37D6-B1AC-9D80DF0655A2> /usr/lib/system/libsystem_m.dylib     0x7fff70bea000 -     0x7fff70c0eff7  libsystem_malloc.dylib (166.220.1) <3B196122-4E0D-3E3F-AA3E-5115B976DE26> /usr/lib/system/libsystem_malloc.dylib     0x7fff70c0f000 -     0x7fff70c1aff3 libsystem_networkextension.dylib (767.220.1) /usr/lib/system/libsystem_networkextension.dylib     0x7fff70c1b000 -     0x7fff70c22fff  libsystem_notify.dylib (172.200.21) /usr/lib/system/libsystem_notify.dylib     0x7fff70c23000 -     0x7fff70c2cfef  libsystem_platform.dylib (177.200.16) /usr/lib/system/libsystem_platform.dylib     0x7fff70c2d000 -     0x7fff70c37fff  libsystem_pthread.dylib (330.220.2) <4958273C-4273-3501-8137-E44249E10D9C> /usr/lib/system/libsystem_pthread.dylib     0x7fff70c38000 -     0x7fff70c3bff7  libsystem_sandbox.dylib (851.220.9) <4D6433A8-C703-3ED9-82EB-B9E481A0FD2F> /usr/lib/system/libsystem_sandbox.dylib     0x7fff70c3c000 -     0x7fff70c3eff3  libsystem_secinit.dylib (30.220.1) <6C681113-8C48-3256-BEF6-0C3723DEB926> /usr/lib/system/libsystem_secinit.dylib     0x7fff70c3f000 -     0x7fff70c46ff7  libsystem_symptoms.dylib (820.227.2) <3147D594-F41F-35FD-BF0B-6B8B66A407DE> /usr/lib/system/libsystem_symptoms.dylib     0x7fff70c47000 -     0x7fff70c5cff7  libsystem_trace.dylib (906.220.1) /usr/lib/system/libsystem_trace.dylib     0x7fff70c5e000 -     0x7fff70c63ffb  libunwind.dylib (35.4) <41222EF6-2233-3CF4-947A-15D48CB8C030> /usr/lib/system/libunwind.dylib     0x7fff70c64000 -     0x7fff70c94fff  libxpc.dylib (1336.220.5) /usr/lib/system/libxpc.dylib External Modification Summary:   Calls made by other processes targeting this process:     task_for_pid: 0     thread_create: 0     thread_set_state: 0   Calls made by this process:     task_for_pid: 0     thread_create: 0     thread_set_state: 0   Calls made by all processes on this machine:     task_for_pid: 51871     thread_create: 0     thread_set_state: 0 VM Region Summary: ReadOnly portion of Libraries: Total=402.3M resident=0K(0%) swapped_out_or_unallocated=402.3M(100%) Writable regions: Total=688.8M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=688.8M(100%)                                 VIRTUAL   REGION REGION TYPE                        SIZE    COUNT (non-coalesced) ===========                     =======  ======= Accelerate framework               128K        2 Activity Tracing                   256K        2 CG backing stores                 1320K        3 CG image                           260K        2 CoreAnimation                     2140K        2 CoreGraphics                         8K        2 CoreImage                           24K        3 CoreUI image data                  104K        2 CoreUI image file                  196K        3 Foundation                           4K        2 Kernel Alloc Once                    8K        2 MALLOC                           223.8M       42 MALLOC guard page                   32K        8 MALLOC_NANO (reserved)           384.0M        2         reserved VM address space (unallocated) STACK GUARD                       56.0M        9 Stack                             11.6M        9 VM_ALLOCATE                       64.8M       31 __DATA                            33.2M      229 __FONT_DATA                          4K        2 __LINKEDIT                       233.7M        5 __OBJC                               8K        2 __TEXT                           168.6M      232 __UNICODE                          564K        2 mapped file                       53.8M       13 shared memory                      632K       11 ===========                     =======  ======= TOTAL                              1.2G      597 TOTAL, minus reserved VM space   851.1M      597 Model: MacBookPro10,1, BootROM 251.0.0.0.0, 4 processors, Intel Core i7, 2.3 GHz, 16 GB, SMC 2.3f36 Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020 Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x112), Broadcom BCM43xx 1.0 (7.77.61.1 AirPortDriverBrcmNIC-1305.2) Bluetooth: Version 6.0.9f2, 3 services, 27 devices, 1 incoming serial ports Network Service: Wi-Fi, AirPort, en0 Serial ATA Device: OWC Aura Pro SSD, 960.2 GB USB Device: USB 2.0 Bus USB Device: Hub USB Device: FaceTime HD Camera (Built-in) USB Device: USB 2.0 Bus USB Device: Hub USB Device: Hub USB Device: Apple Internal Keyboard / Trackpad USB Device: BRCM20702 Hub USB Device: Bluetooth USB Host Controller USB Device: USB 3.0 Bus Thunderbolt Bus: MacBook Pro, Apple Inc., 23.4 From skalogryz.lists at gmail.com Tue Nov 27 14:42:49 2018 From: skalogryz.lists at gmail.com (Dmitry Boyarintsev) Date: Tue, 27 Nov 2018 08:42:49 -0500 Subject: [Lazarus] Lazarus not starting anymore since -r59627 on MacOSX Mojava x86_64 cocoa In-Reply-To: <3d33fe31-6248-2d0e-3fe2-2ab316c30ce6@michael-ring.org> References: <3d33fe31-6248-2d0e-3fe2-2ab316c30ce6@michael-ring.org> Message-ID: On Tue, Nov 27, 2018 at 5:25 AM Michael Ring via lazarus < lazarus at lists.lazarus-ide.org> wrote: > The last working version is -r59626 > Are you using docking? https://bugs.freepascal.org/view.php?id=34593 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mail at michael-ring.org Tue Nov 27 15:04:38 2018 From: mail at michael-ring.org (Michael Ring) Date: Tue, 27 Nov 2018 15:04:38 +0100 Subject: [Lazarus] Lazarus not starting anymore since -r59627 on MacOSX Mojava x86_64 cocoa In-Reply-To: References: <3d33fe31-6248-2d0e-3fe2-2ab316c30ce6@michael-ring.org> Message-ID: <6e1bfb17-0b64-13e9-0e91-9e926109738f@michael-ring.org> Yes, I am using docking and in the crashlog there is also a reference to AnchorDocking. Good to know that there is already an issue for the problem. Michael Am 27.11.18 um 14:42 schrieb Dmitry Boyarintsev via lazarus: > On Tue, Nov 27, 2018 at 5:25 AM Michael Ring via lazarus > > > wrote: > > The last working version is -r59626 > > Are you using docking? > https://bugs.freepascal.org/view.php?id=34593 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: