| delorie.com/archives/browse.cgi | search |
| Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
| List-Subscribe: | <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com> |
| List-Archive: | <http://sourceware.cygnus.com/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT sourceware DOT cygnus DOT com> |
| List-Help: | <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs> |
| Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
| Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
| From: | JSONCRAIG AT aol DOT com |
| Message-ID: | <65.643ef86.268b8ddb@aol.com> |
| Date: | Wed, 28 Jun 2000 13:20:27 EDT |
| Subject: | gdb running in background |
| To: | cygwin AT sourceware DOT cygnus DOT com |
| MIME-Version: | 1.0 |
| X-Mailer: | AOL 4.0 for Windows 95 sub 10 |
Is there some way that one can run gdb so that it will just sit there, and display any OutputDebugString() messages that are called? I know gdb will display them, if you are currently debugging that program, but this seems kind of clunky if I just want to see debug updates, especially if I have more than one executable. Any help is appreciated, Jason Craig -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |