• 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
gdb behaviour..
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gdb behaviour..


  • Subject: gdb behaviour..
  • From: Fons Rademakers <email@hidden>
  • Date: Tue, 02 May 2006 15:26:35 +0200
  • Keywords: CERN SpamKiller Note: -50 Charset: west-latin
  • Organization: CERN

Hi,

I am trying to use gdb via Xcode to debug a large C++ project containing many shared libraries on MacTel. I've a lot of problems with stepping through my code as often a click on "Step Over" results in the same behaviour as "Continue", this is especially bothersome as it requires me to start all over again and only by putting tons of breakpoints along the way I can "guide" gdb to step through the desired code. Is gdb supposed to be this broken on Mac OS X? I am also working on Linux and there gdb is even more broken as it often cannot find class information which is needed to inspect objects. Is there a good alternative (except waiting for Etnus to release totalview for MacTel).

Cheers, Fons.


-- Org: CERN, European Laboratory for Particle Physics. Mail: 1211 Geneve 23, Switzerland E-Mail: email@hidden Phone: +41 22 7679248 WWW: http://fons.rademakers.org Fax: +41 22 7669640 _______________________________________________ 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: gdb behaviour..
      • From: David Dunham <email@hidden>
    • Re: gdb behaviour..
      • From: Jonas Maebe <email@hidden>
  • Prev by Date: Re: Alternative SCM in Xcode
  • Next by Date: Re: gdb behaviour..
  • Previous by thread: Re: Can't add a new build setting
  • Next by thread: Re: gdb behaviour..
  • Index(es):
    • Date
    • Thread