• 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: Finding code exit points w/in gdb
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Finding code exit points w/in gdb


  • Subject: Re: Finding code exit points w/in gdb
  • From: Jonas Maebe <email@hidden>
  • Date: Fri, 6 Aug 2010 20:05:33 +0200

On 06 Aug 2010, at 19:22, Jonathon Kuo wrote:

>  there a way, when running a program in the gdb debugger, to find from what line in the code the program has exited? Is there a way to keep some sort of function invocation call trace? I've inherited some (very) convoluted legacy code and there are times when it will orderly exit from underneath me. Finding all the code execution paths has been difficult.

Set a breakpoint on _exit.


Jonas _______________________________________________
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

References: 
 >Finding code exit points w/in gdb (From: Jonathon Kuo <email@hidden>)

  • Prev by Date: Finding code exit points w/in gdb
  • Next by Date: Static Linking, -syslibroot, and MACOSX_DEPLOYMENT_TARGET
  • Previous by thread: Finding code exit points w/in gdb
  • Next by thread: Static Linking, -syslibroot, and MACOSX_DEPLOYMENT_TARGET
  • Index(es):
    • Date
    • Thread