• 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
Seeing/Viewing/browsing a stacktrace
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Seeing/Viewing/browsing a stacktrace


  • Subject: Seeing/Viewing/browsing a stacktrace
  • From: Brock Brandenberg <email@hidden>
  • Date: Fri, 3 May 2002 10:55:00 -0500

Hi.

Does anyone know of a product or technique to make viewing a stack trace easier than setting a breakpoint in PB with GDB? I have tried doing this with Sample, but it's not easy because of the nature of the way it samples and because it's easy to get lost in the huge number of function calls?

The reason that I ask is that I spend the majority of my learning trying to decipher what the Cocoa frameworks are doing for me behind the scenes and in what order. For instance, when loading data in through an NSDocument subclass, there is a lot of work that Cocoa does for you between the time the user chose the "Open..." menu command and the time the loadDataRepresenation" method gets called. The API docs cover much of the command flow, but it makes it much clearer when you can see the order yourself in a stack trace. However, the stack trace does little to show parameters passed at each function invocation, and it's difficult to step and "browse" without losing track of where you are due to the nature of the way the window scrolls and pops functions off the stack. Are there some fancy tricks with GDB to help?

There appears to be a new product called AppBeat, for this type of functionality, but it appears to be for Carbon apps only and it crashes when viewing the "memory call chain". Doesn't give me much confidence. Should I be telling Sample to look for specific calls? I believe it can do this but I have never used the ability. I don't believe it can store and show parameters for each call though. I know that can require a lot of memory storage, but would be an interesting functionality to see.

Does this make sense to anyone else? Trying to see this helps me fill in the details that the Apple docs are lacking. That is, how it all works together behind the scenes.

Thanks,
Brock Brandenberg

----- industrial design @ bergdesign.com ------
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Prev by Date: Re: Determining connection speed
  • Next by Date: Screen capture?
  • Previous by thread: Re: from bytecodes to native
  • Next by thread: Screen capture?
  • Index(es):
    • Date
    • Thread