Re: Debugging a Curses Program on Mac OS X
Re: Debugging a Curses Program on Mac OS X
- Subject: Re: Debugging a Curses Program on Mac OS X
- From: Keary Suska <email@hidden>
- Date: Wed, 18 Mar 2015 07:44:15 -0600
On Mar 18, 2015, at 6:24 AM, Thomas Wetmore <email@hidden> wrote:
> I am converting an old, large C program that uses curses for its user interface to Mac OS X. It is now ported and partly working.
>
> I am trying to find an effective way to debug the program.
>
> 1. If I try to run it under Xcode’s debugger, because the Xcode debug console does not have a terminal emulator (at least I don’t think it does), weird things happen in the console, and it is difficult to keep things straight in the head.
>
> 2. If I try to run it in its own terminal and attach it to Xcode’s debugger, the very act of going back and forth between the two processes causes the curses system to do things independent of the program, and the program always exits very soon with no apparent cause and hitting no exception breakpoint.
>
> 3. Checking google, the GNU debugger has a “tty” command that can be used to direct the output of a program being debugged to a specific terminal. This seems like the perfect solution for me, but the Xcode debugger does not seem to have this facility.
>
> Currently I’m stuck on option 1 and looking for something better. Any advice? Thanks,
Have you tried running lldb via the command line? This will get you started: https://developer.apple.com/library/mac/documentation/IDEs/Conceptual/gdb_to_lldb_transition_guide/document/lldb-terminal-workflow-tutorial.html#//apple_ref/doc/uid/TP40012917-CH4-SW1
HTH,
Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"
_______________________________________________
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