Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2013-11

Help: OS X Problems

2 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Schindler Karl-Michael
Show quoted text 35 lines
Date: Sun, 3 Nov 2013 00:00:04 -0400 From: Anthony Walter Subject: Re: [Lazarus] Help: OS X Problems To: Lazarus mailing list Message-ID: Content-Type: text/plain; charset="iso-8859-1" My gosh, that's it! The symlink in the MacOS folder was messing up ggdb. Also, I rebuilt everything with -gw. I changed the Project Options | Paths | Target Filename to: $NameOnly($(ProjFile)).app/Contents/MacOS/$NameOnly($(ProjFile)) Which evaluates to: worker.app/Contents/MacOS/worker I can now debug properly. I ran a few tests and for the most part everything was clean, but a few times I got an 'oops' debugger dialog when closing my program: The GDB command: "-file-exec-and-symbols " did not return any result. The GDB process is no longer running. Is there a better option to get rid of the symlink other than setting the target file name like I did? Could someone default the IDE to place the actual exe in app bundles on the mac rather than placing a symlink there instead? I'm writing an exhaustive fpc+lazarus Mac setup guide and I'll be sure to credit you guys. Thanks for the help!

When building lazarus with fink, I replace the symlink by the actual binary. I also compile with OPT='-gw -dDBG_WITH_TIMEOUT'
and also set the option GenerateDwarf for lazarus.

I will be a careful reader of your guide and incorporate your findings in building lazarus in fink.

Unfortunately, I do not have 10.9. I am happy that i could update to 10.7 lately ;-)

Michael Schindler

Reply by email

Martin
to Schindler Karl-Michael
Schindler Karl-Michael wrote
When building lazarus with fink, I replace the symlink by the actual binary. I also compile with OPT='-gw -dDBG_WITH_TIMEOUT'

-dDBG_WITH_TIMEOUT is no longer needed. This was only when the timeout code was new. Now timeout code is always active (unless you deactivate it in the IDE options dialog )

Reply by email