XCode 3 Debugger bug?

  • Hello list,
    I was debugging an app of mine while I've encounter this strange thing (take
    a look at screenshot). This is not the first time.

    <http://img442.imageshack.us/img442/1134/picture2pp3.png>

    There is an NSMutableArray declared and called pdFormat.
    As you can see it was allocated and inited. However I can't see into the
    debugger.
    Some other objects has a <value value instead the address memory.
    Is this a sort of bug of xcode 3 or a mistake of mine? Is there a
    workaround?
    Thanks a lot
    malcom
  • If you can repro this in a sample app, or can send your app to Apple
    as-is, definitely file a bug.

    In my experience the debugger has lots and lots of little issues like
    this, but they never reproduce in a test app; they only start to
    occur when you have a real full-sized app. Our large apps have many,
    many debuggability issues like this screenshot—lots of [$VAR
    whatever] instead of real values, missing variables, <out of scope>
    or <value> where real values ought to be, etc. It's very frustrating
    but there's no way to file a real bug on it because tiny test apps
    never reproduce the bug, and our bugs always get closed with "cannot
    reproduce" when we file them.

    On Nov 21, 2007, at 4:48 PM, malcom wrote:

    > Hello list,
    > I was debugging an app of mine while I've encounter this strange
    > thing (take
    > a look at screenshot). This is not the first time.
    >
    > <http://img442.imageshack.us/img442/1134/picture2pp3.png>
    >
    > There is an NSMutableArray declared and called pdFormat.
    > As you can see it was allocated and inited. However I can't see
    > into the
    > debugger.
    > Some other objects has a <value value instead the address memory.
    > Is this a sort of bug of xcode 3 or a mistake of mine? Is there a
    > workaround?
    > Thanks a lot
    > malcom
  • >> I was debugging an app of mine while I've encounter this strange
    >> thing (take
    >> a look at screenshot). This is not the first time.
    >

      This is more suited for the xcode-users list as it has nothing at
    all to do with Cocoa. For the record, though, I discovered a post on
    xcode-users (of all places) that suggest opening the XCode project
    package (Show Package Contents) and deleting all but the
    project.pbxproj file. This worked for me, but there's probably a
    gentler way to do it (like R'ing TFM and figuring out what's wrong)
    but hey ... ;-)

    --
    I.S.
  • I've tried to remove these files (and xcode cache) but nothing. I've also
    tried to make a new project with sources but nothing has changed. At this
    point I'm making some mistake but I cannot see where.
    I've wrote to Xcode mailing list, meanwhile this is the sources
    (method returnPredicateQueryForFastRules in MCSmartRulesContainer, I've
    setup breakpoints yet).
    This is the link
    http://www.box.net/shared/8cb076nfnq

    On Nov 22, 2007 3:00 AM, I. Savant <idiotsavant2005...> wrote:

    >>> I was debugging an app of mine while I've encounter this strange
    >>> thing (take
    >>> a look at screenshot). This is not the first time.
    >>
    >
    > This is more suited for the xcode-users list as it has nothing at
    > all to do with Cocoa. For the record, though, I discovered a post on
    > xcode-users (of all places) that suggest opening the XCode project
    > package (Show Package Contents) and deleting all but the
    > project.pbxproj file. This worked for me, but there's probably a
    > gentler way to do it (like R'ing TFM and figuring out what's wrong)
    > but hey ... ;-)
    >
    > --
    > I.S.
    >
    >
    >

    --
    Indie Mac Developer
    web: www.malcom-mac.com
    mail: <malcom.mac...>
    aim: malcombsd
  • Wow that's true. Now seems to works well. However I don't remember I've set
    optimization level inside the proj settings. Is it automatically?

    On Nov 22, 2007 11:37 AM, Jack Nutting <jnutting...> wrote:

    > On 11/22/07, malcom <malcom.mac...> wrote:
    >> Hello list,
    >> I was debugging an app of mine while I've encounter this strange thing
    > (take
    >> a look at screenshot). This is not the first time.
    >>
    >> < http://img442.imageshack.us/img442/1134/picture2pp3.png>
    >>
    >> There is an NSMutableArray declared and called pdFormat.
    >> As you can see it was allocated and inited. However I can't see into the
    >> debugger.
    >> Some other objects has a <value value instead the address memory.
    >> Is this a sort of bug of xcode 3 or a mistake of mine? Is there a
    >> workaround?
    >
    > Are you accidentally debugging an optimized binary?  If so, it may
    > have optimized away your local pdFormat variable, sharing the space
    > with fPred (which it can safely do since fPred is only used after your
    > code no longer needs pdFormat).
    >
    > --
    > // jack
    > // http://www.nuthole.com
    >

    --
    Indie Mac Developer
    web: www.malcom-mac.com
    mail: <malcom.mac...>
    aim: malcombsd
  • Well thanks to Jack @ XCode Lists:

    Attach reply:
    -------------------------------------------------------------------------------------------------
    Are you accidentally debugging an optimized binary?  If so, it may
    have optimized away your local pdFormat variable, sharing the space
    with fPred (which it can safely do since fPred is only used after your
    code no longer needs pdFormat).
    -------------------------------------------------------------------------------------------------

    On Nov 22, 2007 10:49 AM, malcom <malcom.mac...> wrote:

    > I've tried to remove these files (and xcode cache) but nothing. I've also
    > tried to make a new project with sources but nothing has changed. At this
    > point I'm making some mistake but I cannot see where.
    > I've wrote to Xcode mailing list, meanwhile this is the sources
    > (method returnPredicateQueryForFastRules in MCSmartRulesContainer, I've
    > setup breakpoints yet).
    > This is the link
    > http://www.box.net/shared/8cb076nfnq
    >
    >
    > On Nov 22, 2007 3:00 AM, I. Savant <idiotsavant2005...> wrote:
    >
    >>>> I was debugging an app of mine while I've encounter this strange
    >>>> thing (take
    >>>> a look at screenshot). This is not the first time.
    >>>
    >>
    >> This is more suited for the xcode-users list as it has nothing at
    >> all to do with Cocoa. For the record, though, I discovered a post on
    >> xcode-users (of all places) that suggest opening the XCode project
    >> package (Show Package Contents) and deleting all but the
    >> project.pbxproj file. This worked for me, but there's probably a
    >> gentler way to do it (like R'ing TFM and figuring out what's wrong)
    >> but hey ... ;-)
    >>
    >> --
    >> I.S.
    >>
    >>
    >>
    >
    >
    > --
    > Indie Mac Developer
    > web: www.malcom-mac.com
    > mail: <malcom.mac...>
    > aim: malcombsd

    --
    Indie Mac Developer
    web: www.malcom-mac.com
    mail: <malcom.mac...>
    aim: malcombsd
previous month november 2007 next month
MTWTFSS
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30    
Go to today