Re: NSObject Foundation tool memory issue?
Re: NSObject Foundation tool memory issue?
- Subject: Re: NSObject Foundation tool memory issue?
- From: Niko Matsakis <email@hidden>
- Date: Thu, 8 Dec 2005 10:46:02 +0100
Bus errors are usually caused my pointers that are not properly
aligned, or other accesses to invalid memory.
If you load this program into gdb and execute it, you will be able to
get a backtrace of where the bus error occurred. Do something like:
gdb -args ./a.out arg1 arg2
(within gdb:)
run
(after crash:)
bt
Niko
On Dec 8, 2005, at 9:17 AM, Lee Cullens wrote:
I'm new to ObjC/Cocoa and have a dumb problem I can't seem to
find. I'm using Terminal gcc to compile and link a small
Foundation Tool I' m working on. I have not really got into Xcode
yet.
Anyway, the short of it is that at the end of my test output I see
the line "Bus error." I "assume" for the moment that it is an
indication of a memory problem in my code, but I'm having problems
tracking it down. I've read everything I could find about memory
management (NSAutoreleasePool) and think I understand ownership,
responsibilities, nested pools and the like.
My question is: What all (generally :-) might cause a Bus error and
is my concentration on a memory management issue a potential
candidate? If it is a memory management issue, what tools,
methods, whatever might help me find the problem. I'm old-school
(a retired SE dating back to the 60's) and have a trace option in
my code, but have not yet been able to find something that might
cause the issue. So I'm resorting to bothering you-all for
possible pointers :-)
Thank you,
Lee C
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden