Re: [Lazarus] Help: OS X Problems

On 03/11/2013 22:49, 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 acti

Re: [Lazarus] Help: OS X Problems

Am 03.11.2013 um 12:00 schrieb lazarus-requ...@lists.lazarus.freepascal.org: > 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

Re: [Lazarus] Help: OS X Problems

Hello, I have made my system ready today. OS X 10.9, fpc 2.6.2, lazarus 1.1. > WE should start a wiki with all the experiences > >> 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 comman

Re: [Lazarus] Help: OS X Problems

On 03/11/2013 04:00, Anthony Walter wrote: 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

Re: [Lazarus] Help: OS X Problems

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 n

Re: [Lazarus] Help: OS X Problems

On 03/11/2013 02:54, Anthony Walter wrote: Dmitry, Thanks. I've read those threads before. I actually have gdb installed through macports and I signed it. Martin, Good information. I ran lazarus with the command line options to log gdb and this is the result: http://cache.codebot.org/stac

Re: [Lazarus] Help: OS X Problems

My other recommendation would be: * create a bug report to adapt the new debugger * don't rely or a debugger being available at all - use logs for debugging. thanks, Dmitry On Sat, Nov 2, 2013 at 9:58 PM, Martin wrote: > On 03/11/2013 01:45, Dmitry Boyarintsev wrote: > > > > > On Sat, Nov 2,

Re: [Lazarus] Help: OS X Problems

Dmitry, Thanks. I've read those threads before. I actually have gdb installed through macports and I signed it. Martin, Good information. I ran lazarus with the command line options to log gdb and this is the result: http://cache.codebot.org/stackoverflow/lazarus-worker-debug.txt Taking you su

Re: [Lazarus] Help: OS X Problems

On 03/11/2013 01:45, Dmitry Boyarintsev wrote: On Sat, Nov 2, 2013 at 9:12 PM, Anthony Walter > wrote: Basically what the video shows is me going through the options screens showing the settings. I am using ggdb, which is the macports version of gdb (Xcod

Re: [Lazarus] Help: OS X Problems

On Sat, Nov 2, 2013 at 9:12 PM, Anthony Walter wrote: > Basically what the video shows is me going through the options screens > showing the settings. I am using ggdb, which is the macports version of gdb > (Xcode no longer comes with gdb). > Was there another thread on this mail list showing how

Re: [Lazarus] Help: OS X Problems

On 03/11/2013 01:12, Anthony Walter wrote: If it helps, I made a short 2 minute video recording of the problem. The microphone wasn't connected properly, so there is no audio, but I think you'll get the idea. Basically what the video shows is me going through the options screens showing the s

Re: [Lazarus] Help: OS X Problems

If it helps, I made a short 2 minute video recording of the problem. The microphone wasn't connected properly, so there is no audio, but I think you'll get the idea. Basically what the video shows is me going through the options screens showing the settings. I am using ggdb, which is the macports

Re: [Lazarus] Help: OS X Problems

Martin, Okay. When I do that, just like when I set the working directory, the window in the program I am debugging is disabled. I cannot raise the window to the foreground by clicking on it. I cannot resize the window. I cannot click the controls. It does not show in the dock. This was something

Re: [Lazarus] Help: OS X Problems

On 02/11/2013 03:59, Anthony Walter wrote: Interesting. Indeed running a program when in the path 'myprogram.app/Contents/MacOS' the windows is enabled and can be interacted with. However, when I set the Working Directory 'myprogram.app/Contents/MacOS' in Lazarus | Run Parameters, the myprogra

Re: [Lazarus] Help: OS X Problems

Interesting. Indeed running a program when in the path 'myprogram.app/Contents/MacOS' the windows is enabled and can be interacted with. However, when I set the Working Directory 'myprogram.app/Contents/MacOS' in Lazarus | Run Parameters, the myprogram window is still disabled. See the screenshot

Re: [Lazarus] Help: OS X Problems

  > Anthony Walter hat am 1. November 2013 um 18:48 > geschrieben: >[...] >  The problem is when I've created an app using fpc/lcl/lazarus and I try to >run it by typing "./myprogram" in a terminal my application form appears, but >controls and entire window is disabled. i cannot even resize the

Re: [Lazarus] Help: OS X Problems

On Fri, Nov 1, 2013 at 1:48 PM, Anthony Walter wrote: > As soon as I add the "gdb" debugger and set the host application to > "/path/to/my/myprogram.app/Contents/MacOS/myprogram", running the app > behaves exactly like I described when run from a terminal like > "./myprgram". That is, the entire

Re: [Lazarus] Help: OS X Problems

Dmitry, I am not too familiar with Mac development. yes I can use the open command to run my apps just fine. The problem is when I've created an app using fpc/lcl/lazarus and I try to run it by typing "./myprogram" in a terminal my application form appears, but controls and entire window is disab

Re: [Lazarus] Help: OS X Problems

Anthony, have you had these kind of issues before with LCL applications? So far, I'm still sure that the problem is with launching the app from the bundle or not. did you try to open the bundle of the application, rather than the application itself? cd "/Users/macuser/Development/Projects/hello"

Re: [Lazarus] Help: OS X Problems

I have yet more details regarding frozen applications... When the IDE options | debugging is set to none the program can be run from the IDE without locking up. When the IDE options | debugging is set to gdb the program fails t run (even if project debugging options are turned off) unless the hos

Re: [Lazarus] Help: OS X Problems

On 30/10/2013 14:32, Anthony Walter wrote: There seems to be some lag between our messages. Anyhow, I create a cert, reboot, and code signed ggdb using the steps provided here and here: http://stackoverflow.com/questions/11504377/gdb-fails-with-unable-to-find-mach-task-port-for-process-id-err

Re: [Lazarus] Help: OS X Problems

To add to my last message, although the programs are frozen, I am able to set breakpoints in my code. For example: procedure TForm1.FormCreate(Sender: TObject); var I: Integer; begin I := Random(100); Caption := IntToStr(I); // breakpoint here end; And the debugger stops on the breakpoint l

Re: [Lazarus] Help: OS X Problems

There seems to be some lag between our messages. Anyhow, I create a cert, reboot, and code signed ggdb using the steps provided here and here: http://stackoverflow.com/questions/11504377/gdb-fails-with-unable-to-find-mach-task-port-for-process-id-error sudo codesign -s ggdb_sodesign /opt/local/b

Re: [Lazarus] Help: OS X Problems (codesigning gdb)

On 30/10/2013 13:57, Anthony Walter wrote: Okay, I set both path and exe encoding to none and am now getting a different informational message when I click the more button: The GDB command: "-exec-run" returned the error: ",msg="Unable to find Mach task port for process-id 6363: (os/kern) f

Re: [Lazarus] Help: OS X Problems

Okay, I set both path and exe encoding to none and am now getting a different informational message when I click the more button: The GDB command: "-exec-run" returned the error: ",msg="Unable to find Mach task port for process-id 6363: (os/kern) failure (0x5).\n (please check gdb is codesigned

Re: [Lazarus] Help: OS X Problems

On 30/10/2013 13:47, Anthony Walter wrote: When I click the more button in the debugger error message box I see this: The GDB command: "-environment-cd "\"/Users/macuser/Development/Projects/hello/hello.app/Contents/MacOS/\""" returned the error: ",msg="\"/Users/macuser/Development/Projec

Re: [Lazarus] Help: OS X Problems

When I click the more button in the debugger error message box I see this: The GDB command: "-environment-cd "\"/Users/macuser/Development/Projects/hello/hello.app/Contents/MacOS/\""" returned the error: ",msg="\"/Users/macuser/Development/Projects/hello/hello.app/Contents/MacOS/\": No such fi

Re: [Lazarus] Help: OS X Problems

On 30/10/2013 12:50, Anthony Walter wrote: Earlier (after my initial post) I had found and read the same links you posted. It feels god knowing I am on the right track, so thanks, thigh I am still having problems. Where I'm At - The lazarus revision 43255 you posted locks up a

Re: [Lazarus] Help: OS X Problems

Earlier (after my initial post) I had found and read the same links you posted. It feels god knowing I am on the right track, so thanks, thigh I am still having problems. Where I'm At - The lazarus revision 43255 you posted locks up at start due to the focus I mentioned previously

Re: [Lazarus] Help: OS X Problems

On 30/10/2013 09:28, Martin wrote: On 30/10/2013 01:56, Anthony Walter wrote: Problem 2 -- http://cache.codebot.org/development/lazarus-run-error.png When I try to run a program (either in debug mode or release mode which has no debugging on) I get that message from OS X. It seems

Re: [Lazarus] Help: OS X Problems

On 30/10/2013 01:56, Anthony Walter wrote: Problem 2 -- http://cache.codebot.org/development/lazarus-run-error.png When I try to run a program (either in debug mode or release mode which has no debugging on) I get that message from OS X. It seems to build fine. I mentioned above t

Re: [Lazarus] Help: OS X Problems

Okay I figured out a few things. Maybe this will be helpful for other people. 1) The only controls which can receive keyboard focus on OS X carbon are text entry controls. If a form is designed with a button or other non text entry control with a tab order of 0, of if active control is set to a no

Re: [Lazarus] Help: OS X Problems

I'd also like to add another note. When I attempt to run the example program which I've named 'hello' from finder (or from a terminal), a console window is displayed along with my simple form. The console has the text... macuser@macpc~/Development/projects/test/hello$ ./hello TCarbonButton.SetFoc

[Lazarus] Help: OS X Problems

Could someone look at screenshots of two problems I'm having on a new OS X system? I'm trying to configure it for trunk fpc and near trunk lazarus development. What's going on -- I installed Xcode with command line tools and used macports to install gdb. I installed fpc 2.6.2