Re: What does crash in setSelectedRanges:affinity:stillSelecting mean?
Re: What does crash in setSelectedRanges:affinity:stillSelecting mean?
- Subject: Re: What does crash in setSelectedRanges:affinity:stillSelecting mean?
- From: Jesse Grosjean <email@hidden>
- Date: Fri, 16 Dec 2005 13:19:13 -0500
Daniel,
And specifically, since you've got your application's call to
"processEditing" in the stack trace, you can set the breakpoing on
setSelectedRanges...+680 only after you've hit a breakpoint where
you call processEditing. Use the po (print-object) command to
examine $r3 to see what object *should* be getting messaged. This
object is either not around or corrupted on your customer's machine.
Thanks. This is what I'm seeing in $r3.
(gdb) po $r3
<MITextView: 0x49404d0>
Frame = {{0.00, 48.00}, {531.00, 278.00}}, Bounds = {{0.00,
0.00}, {531.00, 278.00}}
Horizontally resizable: YES, Vertically resizable: YES
MinSize = {531.00, 278.00}, MaxSize = {531.00, 10000000.00}
That's an NSTextView subclass of mine. Now time for me to think on
why that might be corrupt, but thanks for your help.
_______________________________________________
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