Re: Expanding "this" kills my application
Re: Expanding "this" kills my application
- Subject: Re: Expanding "this" kills my application
- From: Laurence Harris <email@hidden>
- Date: Thu, 6 Dec 2007 16:54:12 -0500
On Dec 6, 2007, at 4:36 PM, Jim Ingham wrote:
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.
Nothing. Just logs for my application and the Dock.
Larry
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:
40apple.com
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