• 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: Expanding "this" kills my application
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Expanding "this" kills my application


  • Subject: Re: Expanding "this" kills my application
  • From: Jim Ingham <email@hidden>
  • Date: Thu, 6 Dec 2007 13:36:46 -0800

You app may have "disappeared" because gdb crashed. Usually you will see some banner to that effect in the Xcode UI, but maybe something else overwrote that before you got a chance to see it.

Check in ~/Library/Logs/CrashReporter

for a gdb-{i386,powerpc}-apple-darwin log file with a current date. If you find that, then apparently printing some ivar of this is causing gdb to crash. If so, please file a bug with the crash log.

Jim

On Dec 6, 2007, at 11:40 AM, Laurence Harris wrote:


On Dec 5, 2007, at 6:04 PM, Chris Espinosa wrote:


On Dec 5, 2007, at 2:49 PM, Laurence Harris wrote:

I'm trying to track down a problem in my application running in Leopard. I get to a point where I stop in the debugger and I want to view the member variables of the current object. I click the disclosure triangle for "this," and about two seconds later my application disappears. This is consistent. Any ideas?

Turn off Data Formatters, first. If that makes your app survivable, that narrows it down.

It doesn't. No difference.

Check to see whether there's anything in Console.app's CrashReporter folder under your app's name. If there are backtraces there it may help us figure out what is actually crashing.

Nothing for these crashes, it just disappears. I'm trying to track down a crash in PlotIconRef, which appears to be the result of a bad IconRef. It just started in Leopard, and I don't know if it's a problem Leopard has exposed in my application or if it's a bug in Leopard, so I'm stopping on a breakpoint before my code that gets the IconRef is called.


Larry

In order to get access to your app's data values, Xcode's data formatters run in your app's process space, so they're subject to all the vagaries of any running code. You could have a bug that's smashing the data formatters. You could have a bad value for a local variable or argument that causes some underlying routine to crash when trying to interpret it (data formatters need to be as fast as possible, so they're not terrifically hardened against bad values).

Chris

_______________________________________________ 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: Expanding "this" kills my application
      • From: Laurence Harris <email@hidden>
References: 
 >Expanding "this" kills my application (From: Laurence Harris <email@hidden>)
 >Re: Expanding "this" kills my application (From: Chris Espinosa <email@hidden>)
 >Re: Expanding "this" kills my application (From: Laurence Harris <email@hidden>)

  • Prev by Date: Re: tDirStatus is an undefined type?
  • Next by Date: Re: Since Xcode 3.0, ld insists on linking CoreData.framework
  • Previous by thread: Re: Expanding "this" kills my application
  • Next by thread: Re: Expanding "this" kills my application
  • Index(es):
    • Date
    • Thread