• 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: sprintf and 64-bit integers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: sprintf and 64-bit integers


  • Subject: Re: sprintf and 64-bit integers
  • From: Andrew Farmer <email@hidden>
  • Date: Mon, 14 Sep 2009 21:54:34 -0700

On 14 Sep 2009, at 11:48, Sean McBride wrote:
On 9/13/09 12:01 PM, Jens Alfke said:
It would be best to convert all your sprintf calls to snprintf, which
is a safer equivalent that won't overflow the buffer.

Yes, sprintf is pure evil. snprintf is less evil.

Also, I recommend adding -fstack-protector -D_FORTIFY_SOURCE=2, they can
help catch some of these problems. And valgrind would probably have
caught this problem immediately.

Sadly, valgrind hasn't yet been updated to run under Snow Leopard. _______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: sprintf and 64-bit integers
      • From: "Sean McBride" <email@hidden>
References: 
 >Re: sprintf and 64-bit integers (From: Greg Guerin <email@hidden>)
 >Re: sprintf and 64-bit integers (From: Jens Alfke <email@hidden>)
 >Re: sprintf and 64-bit integers (From: "Sean McBride" <email@hidden>)

  • Prev by Date: Re: NSOperation and lazy loading
  • Next by Date: Re: NSPopUpButton breaks in Snow Leopard
  • Previous by thread: Re: sprintf and 64-bit integers
  • Next by thread: Re: sprintf and 64-bit integers
  • Index(es):
    • Date
    • Thread