Debugging Carbon Application

[abb]

Hi, All,

I'm trying to launch the project in debugger (using IDE), and my application appears on the screen, but all its controls are unavailable for mouse clicks, and the mouse cursor is "I" (as it is in the editor). I can press the Close/Minimize/Maximize buttons of my application window, so I can terminate it by such click as well as by IDE menu, but I just can't test my application because I can't click controls in its window. Therefore I can't debug it as I can't activate the piece of code with the breakpoint.  

May it so happen because it is just an executable but not the APP structure? If so, maybe it would be a solution to prepare APP structure with all nesessary files and assign the compiled application path in Lazarus settings to the Contents/macos/ subdirectory of this APP structure? Will IDE then be able to run my project correctly?

Is there anybody here, who ever tried to debug Carbon application? I understand that Carbon widgetset is yet under construction but may be there are any testers here?

Thanks.

[Phil]

I'm trying to launch the project in debugger (using IDE), and my application appears on the screen, but all its controls are unavailable for mouse clicks

I don't think this has anything to do with the debugger, but that you're running the executable, not the application.

Debug the application:

 gdb project1.app/contents/macos/project1

[Marc]

indeed, you need some basice .app structure like in  http://lazarus.dommelstein.net/examples/cursors/project1.app

inside MacOS, project1 is a symlink: project1 -> ../../../project1

when you specify in Run parameters -> host application : project1.app/contents/macos/project1
you can debug from lazarus

[abb]

specify in Run parameters -> host application : project1.app/contents/macos/project1
you can debug from lazarus

Yes! Now I can click buttons in my application... but breakpoint is not working.

Linking options are set:
- generate debug info for gdb
- generate debug info for dbx
- display line numbers
- use heaptrc unit
- generate code for valgrind
-generate code for gprof

Linking options are off:
- Strip symbols from executable is
- link smart
- win32 gui application

What I may do yet wrong?
Thanks.

[Marc]

Guessing, do you have an intel mac ?

[abb]

Guessing, do you have an intel mac ?

Yes. IC2D

Any ideas of how to configure debugger options?

Thanks.

[Marc]

You're the second intel (*) mac where setting breakpoints doesn't work. I'm thinking of a testcase on how to check whats going on.

(*) I don't know if it is cpu related, I only know that it works on my powerPC mini (and I can't remember these problems reported before intel mac was available)

[abb]

You're the second intel (*) mac where setting breakpoints doesn't work. I'm thinking of a testcase on how to check whats going on.

Am looking forward to any ideas you may have! This problem really stops my further experimenting with Lazarus on Mac

Thanks.

[abb]

You're the second intel (*) mac where setting breakpoints doesn't work. I'm thinking of a testcase on how to check whats going on.

Am still looking forward to any ideas!

Is there any location here, where I need to post a bugreport?

I see some debugging trace info, including some error messages in the X11 terminal window, and it is helpful information, but I can't really work with debugger without breakpoints.

Thanks.

[Marc]

A link to the bugrtacker is given on this page. Just look in the left column under the heading: Code & Coding -> Bug tracking

[vaso]

I have same issue:
Mac OS X Tiger Intel
and installed from daily snapshots
fpc-2.1.5-20070524-i386-macosx.dmg
fpcsrc-2.1.5-20070524-i386-macosx.dmg
lazarus-0.9.23-20070524-i386-macosx.dmg
and gdb installed frm sources (last release). in terminal typed ./configure
and after that ./make
Thank you.