To: djgpp AT delorie DOT com
Date: Thu, 9 Mar 2000 14:49:44 -0500
Subject: Is dual monitors necessary?
Message-ID: <20000309.144953.-398953.1.roberts.j.whitlock@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-1,11-12,17-24
X-Juno-Att: 0
X-Juno-RefParts: 0
From: Robert S Whitlock <roberts DOT j DOT whitlock AT juno DOT com>
Reply-To: djgpp AT delorie DOT com

Hi there

I'm getting into the realm of debugging with gdb. I've picked up the GNU
docs for gdb and read some of them. I can now do basic debugging tasks
like running the program, setting breakpoints, looking at the stack, etc,
etc. But the program I need to debug is a graphics app, and whenever I
set a breakpoint after the program switched to graphics mode, the
breakpoint works fine.... but the monitor remains in that graphics mode
and not the one gdb is using. I can type "shell edit" and it will switch
back to desktop and edit will be there and that's just fine and dandy,
and when I exit from edit the graphics mode screen comes back again and
that's fine, but I can never get to see the actual gdb prompt.

Do I need a dual monitor setup? Is that the only/recommended way of
debugging graphics apps? I got a coupla' 16-color monitors down in the
basement, would those work? (yeah, I got cards for them somewhere, too) I
would like to avoid a dual setup for now particularly since I really do
not have the desk space for a second monitor.

Any help is (obviously) welcomed.


--Robert Whitlock
http://www.geocities.com/CapeCanaveral/Hangar/9520/
ICQ 60123256