delorie.com/archives/browse.cgi | search |
Xref: | news2.mv.net comp.os.msdos.djgpp:3549 |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: gdb and stdout |
Date: | Tue, 07 May 1996 11:25:30 CDT |
Organization: | Rice University, Houston, Texas |
Lines: | 6 |
Message-ID: | <318f797a.sandmann@clio.rice.edu> |
References: | <Pine DOT SUN DOT 3 DOT 91 DOT 960506091015 DOT 13129K-100000 AT is> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
NNTP-Posting-Host: | clio.rice.edu |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
> Under MS-DOS, the gdb and the debuggee share file handles, ... > Solutions? I can think about a few: What I did for edebug/fsdb was to change the debugger stdout handle to something different (via a dup?) before starting the child. It's been too long now to remember what I did, but this might be a workaround.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |