Re: gdb breaks on _NSRaiseError
Re: gdb breaks on _NSRaiseError
- Subject: Re: gdb breaks on _NSRaiseError
- From: Quentin Mathé <email@hidden>
- Date: Sat, 21 Jun 2003 20:38:54 +0200
Le samedi, 21 juin 2003, ` 18:41 Europe/Paris, Shawn Erickson a icrit :
On Friday, June 20, 2003, at 03:03 PM, Quentin Mathi wrote:
Although I have no symbolic breakpoint on -[NSException raise] or on
raise function (I checked with "info breakpoints"), gdb is breaking
on the function _NSRaiseError, is this normal ? I remember before to
have see the application and gdb to exit together on an exception
(with Project Builder 1.x).
If it's normal, what's the purpose now of for example "break raise"
(or -[NSException raise] symbolic breakpoint) ?
ps : the stack trace is :
_NSRaiseError
+[NSException raise:format:]
-[NSCFArray objectAtIndex:]
If you are running the debugger and are using a debug build of your
application I bet it will break into the debugger when an exception
happens.
Anyway, you are doing something when calling objectAtIndex: that is
throwing an exception. Most likely you are using an index that is out
of bounds.
I choose that, to use an index out of bounds to have an exception.
but what I don't understand is what is the use of -[NSException
raise] symbolic breakpoint if the application breaks into the debugger
when an exception is thrown.
--
Quentin Mathi
email@hidden
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.