iOS iPhone development interfering with Terminal.app?

Luke Redpath

macrumors 6502a
Original poster
Nov 9, 2007
731
6
Colchester, UK
This might seem like a strange one, but I almost always have Terminal.app running for one reason or another, especially when developing as I am using Git for version control.

It does seem however that after an extended period of development time in XCode with the iPhone SDK (and the many build cycles that come with it) that I'm an unable to start any more terminals (either in a new tab or by restarting Terminal.app completely). Instead I get the error:

"Could not open a new pseudo-tty."

Googling for this revealed little, except for one relatively old post related to using the iPhone SDK:

http://blogs.oreilly.com/iphone/2008/03/fixing-terminal-tty-errors.html

It's suggestion is to reboot the machine which in my experience is the only way to solve the problem

Does anybody else have this issue? What could be causing it? It's very strange and very frustrating.
 

RossOliver

macrumors regular
Nov 6, 2006
157
0
This might seem like a strange one, but I almost always have Terminal.app running for one reason or another, especially when developing as I am using Git for version control.

It does seem however that after an extended period of development time in XCode with the iPhone SDK (and the many build cycles that come with it) that I'm an unable to start any more terminals (either in a new tab or by restarting Terminal.app completely). Instead I get the error:

"Could not open a new pseudo-tty."

Googling for this revealed little, except for one relatively old post related to using the iPhone SDK:

http://blogs.oreilly.com/iphone/2008/03/fixing-terminal-tty-errors.html

It's suggestion is to reboot the machine which in my experience is the only way to solve the problem

Does anybody else have this issue? What could be causing it? It's very strange and very frustrating.
I've had the same thing since I started developing for the iPhone - it seems to come and go... a real pain though because it stops any output working (so printf's and NSLogs etc)...

-Ross
 

vladinecko

macrumors member
Nov 3, 2006
66
0
Bay Area, CA
I've had the same thing since I started developing for the iPhone - it seems to come and go... a real pain though because it stops any output working (so printf's and NSLogs etc)...
the messages are still logged in the console (os x console, not the xcode one) so you can track them there as well.