• 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: I found a Clang analyzer bug!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: I found a Clang analyzer bug!


  • Subject: Re: I found a Clang analyzer bug!
  • From: Sean McBride <email@hidden>
  • Date: Wed, 19 Mar 2014 14:49:27 -0400
  • Organization: Rogue Research Inc.

On Wed, 19 Mar 2014 11:05:55 -0700, Matt Neuburg said:

>What's the appropriate way to report this? Should I just use the
>bugreporter, or does this need to go to the clang folks? Thx - m.

If you can repro with Xcode, file the bug in Radar.  If you can also repro with your own build of the open source clang (svn trunk), also file a bug at <http://llvm.org/bugs>.

Cheers,

--
____________________________________________________________
Sean McBride, B. Eng                 email@hidden
Rogue Research                        www.rogue-research.com
Mac Software Developer              Montréal, Québec, Canada



 _______________________________________________
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: 
 >I found a Clang analyzer bug! (From: Matt Neuburg <email@hidden>)

  • Prev by Date: Re: why are conditional breakpoints SO SLOW?
  • Next by Date: Re: Help! Any way to debug the App Store binary?
  • Previous by thread: I found a Clang analyzer bug!
  • Next by thread: Re: I found a Clang analyzer bug!
  • Index(es):
    • Date
    • Thread