• 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: breaking on console output
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: breaking on console output


  • Subject: Re: breaking on console output
  • From: Andreas Grosam <email@hidden>
  • Date: Fri, 14 Sep 2012 16:19:32 +0200

On 14.09.2012, at 15:59, Steve Mills wrote:

> On Sep 14, 2012, at 00:57:53, Jens Alfke <email@hidden> wrote:
>
>> There are a lot of different calls that will produce console output. This looks like NSLog output, I think, so try setting a breakpoint on NSLog. (Go to the breakpoints pane in Xcode and click on the “+” button at the bottom to add a symbolic breakpoint.)
>
> Ah, thanks. I'm glad I can use Xcode for this. Sadly, it's not NSLog that's spitting out this message. I also tried printf and fprintf. Is there something at an even lower level that these types of calls might go through?

write, pwrite, writev

maybe.




 _______________________________________________
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: breaking on console output
      • From: Steve Mills <email@hidden>
References: 
 >breaking on console output (From: Steve Mills <email@hidden>)
 >Re: breaking on console output (From: Jens Alfke <email@hidden>)
 >Re: breaking on console output (From: Steve Mills <email@hidden>)

  • Prev by Date: Re: breaking on console output
  • Next by Date: Re: breaking on console output
  • Previous by thread: Re: breaking on console output
  • Next by thread: Re: breaking on console output
  • Index(es):
    • Date
    • Thread