Home/ Questions/Q 728401
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T06:40:37+00:00

I’ve declared a struct in my header file like this: typedef struct { NSString

  • 0

I’ve declared a struct in my header file like this:

typedef struct {
NSString *department;
NSString *departmentId;
}  Department;

Department currentDepartment;

This struct is in a fairly simple class. I assign the struct values in viewDidLoad. Just before leaving viewDidLoad, I see the struct values are still there. After the user clicks a segment control, I reassign the struct values. Before assigning values, I see the two struct values are 0x0. I do have NSZombieEnabled, which is printing out this when I mouse over the struct while the app is running and one of my breakpoints have been hit:

MyApp[25722:207] *** -[CFString _cfTypeID]: message sent to deallocated instance 0xfc0e90

I’m not creating an instance of the struct or deallocating it. How can it be getting deallocated?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I strongly advise against putting objects in structs if at all possible. Structs are just dumb collections of data and cannot manage their members’ memory like objects can with accessors. This means client code will have to take on the responsibilty of retaining and releasing the structs members whenever it deals with them and making sure they are released before the strict goes out of scope — it’s not really that easy. You’d be better off creating a lightweight object.

    • 0