Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Rolf Buenning Newsgroups: comp.lang.pascal.misc Subject: Re: Do'nt know Date: 22 Aug 2025 06:07:55 GMT Lines: 42 Message-ID: References: Reply-To: Rolf Buenning X-Trace: individual.net OqjroZ2b+Vkayl5Gbk/0GAKmrbiPo/fRHrTlUdiForV8lIqU4q Cancel-Lock: sha1:ruBowP/QyCNCzF/MYkInngQrIUM= sha256:WLPUG7kSdnKUU/lxAQlFVNSbnG6pw3eFYgJw3y0iU3w= User-Agent: slrn/1.0.3 (Linux) Xref: csiph.com comp.lang.pascal.misc:2810 On Thu, 21 Aug 2025 17:42:30 -0000 (UTC), David LaRue tippte: > Rolf Buenning wrote in news:mgoe8bFj0oiU1 > @mid.individual.net: > >> >> Hi, >> >> Sorry, if I make mistakes in this english. >> >> I try to make a application in free-pacal, ide is lazarus. >> All things looked good up to yesterday or so. >> >> The application has few units and forms, which will be started from >> a main-form via button-click event with form.showmodal. >> >> Now if I start the application, it jumps right into the middle of >> the application whithout all steps before whithout main-form etc. >> >> How can I find the mistake. >> >> I would be happy about answers. >> > > Unless you have a serious number of procedures the easiest method to figure > this out without a debugger is to log to the console or a "log file" and > set up 'log entries' along the path you expect plus along the path to the > procedure that was unexpected. While doing this step you might find your > answer in an unexpected call to the offending procedure. > > Run the application once. Then examine the output log (screen or log file) > to find the procdure that was called unexpectedly. You can also pipe the > output to a log file on most operating systems; it just takes more typing > when starting the application. > > Modify the log entries as needed to fine tune the results. > > Some compilers have a compile switch that will do this for you > automatically. Thanks, I will try that and tell later about it. -- Gruss Rolf