Cocoa Debugging: what changed

Revision 1 to 2. Removed lines have a minus sign; added lines have a plus sign.

Old	New		Line
1	1		(macOS only)
2	2
3	3		Having problems running a project compiled for Cocoa? Here are steps to try
4	4
5	5		## Run from Terminal
6	6
7	7		- open up a Terminal (Applications -\> Utilities -\> Terminal).
8	8		- cd to your project directory
9	9		- cd to the bundle (a bundle is a specially structured directory where binary resides. The bundle directory extension is ".app" )
10	10
11		-	~~` cd project1.app/Contents/MacOS`~~
	11	+	```
	12	+	cd project1.app/Contents/MacOS
	13	+	```
12	14
13	15		(for your project "project1.app" needs to be changed to your project's name)
14	16
15	17		- run the project
16	18
17		-	~~`./project1`~~
	19	+	```
	20	+	./project1
	21	+	```
18	22
19	23		See the output! The output might suggest what's going on. Any OS or error warning messages should be shown.
20	24
21	25		### Console App
22	26
23	27		The log entries could also be acquired from Console utillity.
24	28
25	29		## Run with lldb debugger
26	30
27	31		Repeat the same steps as in "Run from Terminal", but run the program as
28	32
29		-	~~`lldb project1`~~
	33	+	```
	34	+	lldb project1
	35	+	```
30	36
31	37		(loading of lldb requires admin rights, and well as takes some time) once loaded enter command
32	38
33		-	~~`r`~~
	39	+	```
	40	+	r
	41	+	```
34	42
35	43		and wait for it to stop or catch the application crash. See more [[lldb\|here]]
36	44
37	45		## Troubleshooting
38	46
39	47		- if a project can compile and run for Carbon, yet it cannot do the same for Cocoa, then the issue is likely with Cocoa widgetset. Creating a minimal sample project is suggested
40	48		- if a project runs but does nothing and provides a constant CPU load (i.e. 99%, 50% or 25%, depending on the number of cores), then there's an endless loop triggered by some code.
41	49
42	50		## Creating a Minimal Sample Project
43	51
44	52		It's likely you would encounter a problem when working with a big production project.
45	53
46	54		It's likely you might have some closed-source code that you're not allowed to share.
47	55
48	56		It's preferred to have a simple project demonstrating the problem. "Simple" meaning:
49	57
50	58		- it's small in size one (or two) forms only.
51	59		- minimal set of controls
52	60		- NO external package dependencies (packages supplied with Lazarus are ok)
53	61
54	62		In order to get a simple project from the big production project you can do the following:
55	63
56	64		- copy the project stand-alone (not to harm the existing code base)
57	65		- remove (delete) pieces that are not related to the bug
58	66
59	67		:* (i.e. if you're having problems with placement of a control, you might want to remove main menu, TActions, if any)
60	68
61	69		:* remove bigger pieces first (it might be much easier than you think)
62	70
63	71		- after each piece is removed, run the project, to make sure you're still getting the error.
64	72		- keep removing code (and reference to any other external dependencie) until you reach the point that you cannot remove anything without affecting the bug.
65	73
66	74		At this point you should have small enough project to demonstrate the problem and [[How do I create a bug report\|bug report it]].
67	75
68	76		## See also
69	77
70	78		- [[How do I create a bug report]]
71	79		- [[lldb]]
72	80		- [[Cocoa Interface]]
73	81		- [Apple: Appendix A: LLDB for GDB Users – Command Summary](https://developer.apple.com/library/archive/documentation/General/Conceptual/lldb-guide/chapters/A3-GDB-Summary.html)
74	82
75	83		---
76	84		From the Free Pascal wiki, page "Cocoa Debugging", as it stood on 2020-08-06 after a change by Trev, out of the wiki's dump of 2024-05-26. Copyright stays with the author who wrote it, according to the old wiki's [[Licensing]] page. If you have concerns about this material, [message the admin](/wiki-contact).
77	85		Category: Cocoa
78	86		Category: Debugging
79	87		Category: macOS

Back to history