Article View: comp.unix.programmer
Article #14Re: Debugging full-screen programs?
From: Dave Woerner
Date: Wed, 28 Oct 1992 17:52
Date: Wed, 28 Oct 1992 17:52
18 lines
1121 bytes
1121 bytes
jason@jarthur.claremont.edu (Jason Merrill) writes: >The traditional gdb/dbx interface fails miserably if the program you are >trying to debug wants to take over the whole screen. How can I debug >programs like this? Mips's version of dbx allow you to re-direct your I/O to another tty on the run command. I don't know if other platforms have this feature. >I am using screen 3.2, but if I tell the program to use another screen tty, >the program that was already using that tty tends to fight bloody war with >the program I am trying to debug over control of the tty. Have you tried putting the shell that is using the other tty to sleep? I find "sleep 100000" does the job nicely. Dave
Technical Details
Message-ID:
<49054@shamash.cdc.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!ogicse!network.ucsd.edu!sdcrsi!equalizer!timbuk.cray.com!shamash!dbwReferences:
<1992Oct28.062513.15742@muddcs.claremont.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!ogicse!network.ucsd.edu!sdcrsi!equalizer!timbuk.cray.com!shamash!dbw From: dbw@svl.cdc.com (Dave Woerner) Newsgroups: comp.unix.programmer Subject: Re: Debugging full-screen programs? Message-ID: <49054@shamash.cdc.com> Date: 28 Oct 92 17:52:49 GMT Article-I.D.: shamash.49054 References: <1992Oct28.062513.15742@muddcs.claremont.edu> Sender: usenet@shamash.cdc.com Lines: 18