• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Funky Xcode crashing-my-app behavior
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Funky Xcode crashing-my-app behavior


  • Subject: Re: Funky Xcode crashing-my-app behavior
  • From: Christopher Friesen <email@hidden>
  • Date: Thu, 7 Aug 2008 14:18:54 -0700

Which version of Xcode are you using? We recently stopped evaluating expressions when the expressions window is closed.

-ChrisF

On Aug 6, 2008, at 9:25 PM, Randall Meadows wrote:

On Aug 6, 2008, at 7:25 PM, Ken Thomases wrote:

I wonder if you don't have something in your Expressions window that's being repeatedly re-evaluated. If it's an expression including a function or method call, it might be operating on a stale or invalid pointer and causing your exception.

AAAAAHHHHHHH!!!!!! In the words of a famous TV personality: "I LOVE YOU MAN!!!"[1]


I've re-installed Xcode twice, and was about to migrate to a new user account (where the problem wasn't occurring) and deal with the attendant headaches of doing so. But one stroke of the delete key in the Expressions window was all that was needed. I hardly *ever* use that window; this morning was probably the first time in 4-5 months, and then I closed it and thought nothing more of it.

Thank you thank you thank you! If we ever meet at WWDC, C4, etc., Ken, drinks are on me.[2]
randy


[1] <http://www.youtube.com/watch?v=AYNNH8WX9Eo>
[2] You'll have to remind me, though, because as I've just shown, my memory ain't what it used to be. ;)


Among the things you reported deleting, you did not say if you deleted the $USER.* files within the project package.

Cheers,
Ken

On Aug 6, 2008, at 7:07 PM, Randall Meadows wrote:

I'll do that, but in the mean time, here's one more data point:

On the same project, not even rebuilding it, everything works just fine on another user account on the same machine.

I've tried re-installing Xcode from scratch (using the uninstall- devtools script), and deleted everything else I can think of/find, including com.apple.Xcode.plist, the /Library/AppSupp and ~/ Library/AppSupp Xcode and Developer stuff, caches galore, but still my main account is screwed, another clean account is not.

randy

On Aug 6, 2008, at 4:08 PM, Jim Ingham wrote:

<function called from gdb> is just what it sounds like, for some reason gdb is calling a function in the program being debugged. gdb does that on the stack of the current thread, and this is just the marker for where the gdb controlled part of the stack starts.

It looks like maybe this is an NSMenu data formatter, since its calling some NSMenu introspection function. Calling that function is raising an NSException, and that's in turn hitting your breakpoint. I think if you just continue here, it should be okay. If that doesn't work, do:

(gdb) frame 12
(gdb) return

It's odd that something a data formatter is doing is causing an exception to be raised. If you can file a bug with the Xcode/gdb log included (you can turn on this logging in the Debugging pane of the Xcode Preferences) I can tell for sure what we were trying to do when we went to call this, and maybe why it went wrong.

Thanks,

Jim

On Aug 6, 2008, at 2:01 PM, Randall Meadows wrote:

Ok, strange subject line, I know; I'm not sure really how to phrase it.

I have a menu item "Batch Edit", whose sent action is "batchEdit:", to First Responder. I have "batchEdit:" defined in a window controller.

"All of a sudden"* when I select that menu item (I get a slightly different stack trace depending on whether I select it using the mouse or command key, but the top 16 [0-15] entries in the stack trace remain the same either way), "batchEdit:" is called, and a breakpoint on the first line is hit. The first line is NSLog(@"entering batchEdit:");. By the time that BP is hit, this is printed in the console window:

2008-08-06 14:43:28.378 Assets Manager[3332:817] *** - [NSApplication length]: unrecognized selector sent to instance 0x114a70

When I stop over the NSLog call, I end up with this crash (I have BPs set on [NSException raise] and objc_exception_throw):
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users 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. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Funky Xcode crashing-my-app behavior
      • From: Randall Meadows <email@hidden>
References: 
 >Funky Xcode crashing-my-app behavior (From: Randall Meadows <email@hidden>)
 >Re: Funky Xcode crashing-my-app behavior (From: Jim Ingham <email@hidden>)
 >Re: Funky Xcode crashing-my-app behavior (From: Randall Meadows <email@hidden>)
 >Re: Funky Xcode crashing-my-app behavior (From: Ken Thomases <email@hidden>)
 >Re: Funky Xcode crashing-my-app behavior (From: Randall Meadows <email@hidden>)

  • Prev by Date: Re: Gcc warning instead of error (followup)
  • Next by Date: Re: Funky Xcode crashing-my-app behavior
  • Previous by thread: Re: Funky Xcode crashing-my-app behavior
  • Next by thread: Re: Funky Xcode crashing-my-app behavior
  • Index(es):
    • Date
    • Thread