• 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: How to dump core?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to dump core?


  • Subject: Re: How to dump core?
  • From: Prachi Gauriar <email@hidden>
  • Date: Thu, 11 May 2006 00:02:42 -0400


On May 10, 2006, at 9:20 PM, Ken Turkowski wrote:

I'm doing some unit testing by compiling directly with gcc in Terminal, and running as a command line tool, and I get a segmentation fault. When I run in GDB, it runs fine. How can I get it to dump core when running from the command line? Or do you have some alternative debugging strategies?

Another option is to just view the crash log in ~/Library/Logs/ CrashReporter/processName.log. This gives you a stack trace for each running thread, as well as register contents and any libraries that are loaded in your app.


-Prachi
_______________________________________________
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: How to dump core?
      • From: Scott Ribe <email@hidden>
References: 
 >How to dump core? (From: Ken Turkowski <email@hidden>)

  • Prev by Date: Re: Programmatically changing "Open using Rosetta" flag
  • Next by Date: why: sClientMessageProc == nil CoreDockRegisterClient_AlreadyRegistered on startup?
  • Previous by thread: Re: How to dump core?
  • Next by thread: Re: How to dump core?
  • Index(es):
    • Date
    • Thread