CodeWarrior freezes when debugging using "Terminal I/O" setting

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Joakim Nyström - 07 Feb 2005 15:35 GMT

I have some problems when I try to debug and the "Use Terminal for
standard in/out" setting is checked.
(CodeWarrior->Preferences->Debugger->Mac Os X
Debugger). Everything is fine until the message "Loading debugging data
for..." is shown. Now the program becomes unresponsive and you get the
infamous "spinnning beachball"
Since the built-in window for standard in/out is painfully slow this is
quite a big issue for me.

After some research I found that CodeWarrior is trying to access a file
named "/tmp/CWTermSettings" which does not exist. It continues forever
trying this but if you do a "touch /tmp/CWTermSettings" the deadlock is
solved. However you still get the built-in window for I/O instead of a
Terminal window.

What could be the cause of this problem? Corrupt settings files?
(I know gdb is installed and working)

Thanks,

Joakim Nyström

Reply to this Message

Joakim Nyström - 07 Feb 2005 15:38 GMT

Forgot to mention I'm using CodeWarrior 9.4

/ Joakim Nyström

Reply to this Message

MW Ron - 16 Feb 2005 00:33 GMT

>I have some problems when I try to debug and the "Use Terminal for
>standard in/out" setting is checked.
[quoted text clipped - 13 lines]
>What could be the cause of this problem? Corrupt settings files?
>(I know gdb is installed and working)

I don't have any explanation, my guess is your set up is wrong in some
way. Read the release notes on Making_Mach-O_Projects_Note.txt and the
MSL C Release notes to be sure you have the right setup and mix of
settings and libraries etc.

Ron

Signature

Metrowerks Community Forum is a free online resource for developers
to discuss CodeWarrior topics with other users and Metrowerks' staff
-- http://www.metrowerks.com/community --

Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com

Reply to this Message

Joakim NystrÃ¶m - 18 Feb 2005 09:02 GMT

Thanks for your answer.

Fortunately the project that failed before has started to work again.
Unfortunately I don't know why. This seems to be the nature of my
problem, it comes and it goes away. Of course there has to be
something different between the runs. However, when I have the problem
I've tried to do a really simple program, like running the default
"C++ Console Mach-O" project and even then I get the problem. Because
of this I don't think it's related to a bad mix of settings and
libraries but I will certainly have a thorough look into this.

I have also noticed some strange things regarding the debug settings
that may be related to my problem. Occasionally I get the built-in window
for standard in/out even though the "Use Terminal for standard in/out"
is checked.

Is there anything I can test to get more information for you whenever
I get the problem again? There must be something wrong when the IDE
is looking forever for the file (/tmp/CWTermSettings). What is the
purpose of this file, by the way? I'm more than happy to help.

Thanks again,

Joakim

--
Joakim Nystrom
Developer
Propellerhead Software AB

Reply to this Message

MW Ron - 23 Feb 2005 04:21 GMT

>Thanks for your answer.
>
[quoted text clipped - 16 lines]
>is looking forever for the file (/tmp/CWTermSettings). What is the
>purpose of this file, by the way? I'm more than happy to help.

I believe you said you trashed the Metrowerks preferences in the
Users/username/library/preferneces folder if not trash that. Was
this a command line program, it could be that the settings for it are
wrong. One other thing is that your system might need reinstalling. I
can't think of anything that needs to be searched in a temp file
location.

Ron

Signature

Reply to this Message

Mac Forum / Programming / CodeWarrior / February 2005

CodeWarrior freezes when debugging using "Terminal I/O" setting