• 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: Jonas Maebe <email@hidden>
  • Date: Sat, 15 Sep 2012 01:24:04 +0200

On 14 Sep 2012, at 17:02, Steve Mills wrote:

> On Sep 14, 2012, at 09:19:32, Andreas Grosam <email@hidden>
> wrote:
>
>> write, pwrite, writev
>>
>> maybe.
>
> Every other message stopped on write, but not the one in question. Grrr. Thanks for the help, everybody. Since it's not our code that's doing it, I guess I'll just forget about it.

You can try running the program through dtruss (or dtruss -s to get stack backtraces) to find out which system call is being used. Note that dtruss cannot deal with spaces in file names (my radar filed against Mac OS X 10.5 is still open at least; I'm still on 10.6 myself).


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: 
 >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>)
 >Re: breaking on console output (From: Andreas Grosam <email@hidden>)
 >Re: breaking on console output (From: Steve Mills <email@hidden>)

  • Prev by Date: Xcode folder for xcode-select
  • Next by Date: Re: Xcode folder for xcode-select
  • Previous by thread: Re: breaking on console output
  • Next by thread: Re: breaking on console output
  • Index(es):
    • Date
    • Thread