• 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: Globals Browser (does it work?) [SOLVED (sort of)]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Globals Browser (does it work?) [SOLVED (sort of)]


  • Subject: Re: Globals Browser (does it work?) [SOLVED (sort of)]
  • From: Bill Monk <email@hidden>
  • Date: Tue, 21 Feb 2006 11:54:57 -0600


On Feb 21, 2006, at 7:58 AM, Frank Rimlinger wrote:

Better yet, try loading the debugging symbols for the relevant for the libraries you wish to browse. See "Viewing Shared Libraries" in the Xcode documentation.



Which worked, but it's the last place in the world I would have expected to go in order to load debugging symbols for my source code.

The globals I'm interested in are defined in a file named (duh) globals.c. They are declared extern in globals.h, which is of course #included by files needing the globals.

In the Shared Library browser, a globals.ob entry appears. It's Current Level was set to "-". I changed the popup to "All". XCode immediately changed it back to "-". After doing this several times, it finally stayed set to "All".

Back in the Globals Browser, the symbols in globals.c finally appear and can be check-marked. These now correctly appear in the debugger window under the Globals disclosure triangle.

Odd thing about that disclosure triangle: when there were no globals available to be displayed, clicking it helpfully opened the Globals Browser. Now that there are some globals checked in the Browser, clicking the disclosure triangle to close it causes it to rotate back to its right-pointing orientation, the gloabls text will flicker, then the triangle immediately jumps back to pointing down.

If I click on it 6 times, it finally stays closed. Clicking it again opens the disclosure and shows the globals checked in the browser - that's good. But apparently now the handy shortcut of opening the Browser window is disabled.

Although,really, it wasn't all -that- handy a shortcut, since it didn't help get a global displayed. A much, MUCH better UI design* would be for the first click on the Globals disclosure triangle to open the Shared Libraries browser. Then, once the user has selected the object files for their own source in the Shared Libraries browser, a second click on the Globals disclosure would open Globals Browser.

(* where "much, MUCH, better UI design" means only "far better than the current mess")

So, question answered: Globals Browser -does- work. The process of getting it to work is absurd (and I would love to see someone demo it to Steve). But the Browser itself is fine.

.
_______________________________________________
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: Globals Browser (does it work?) [SOLVED (sort of)]
      • From: Chris Friesen <email@hidden>
References: 
 >Globals Browser (does it work?) (From: Frank Rimlinger <email@hidden>)

  • Prev by Date: Re: No such file or directory
  • Next by Date: Backward compatibility
  • Previous by thread: Globals Browser (does it work?)
  • Next by thread: Re: Globals Browser (does it work?) [SOLVED (sort of)]
  • Index(es):
    • Date
    • Thread