public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: asmwarrior <asmwarrior@gmail.com>
To: gdb@sourceware.org
Subject: [Mingw, GDB MI] console redirect question
Date: Mon, 23 Apr 2012 01:03:00 -0000	[thread overview]
Message-ID: <4F94AA91.3060608@gmail.com> (raw)

I'm using GDB MI interface to debug Codeblocks.(Debug Codeblocks under Codeblocks)
Windows XP, GDB CVS build under MinGW GCC 4.6.x.
I experience a problem that the debuggee Codeblocks's log message was show in the GDB MI's log.
This is quite annoying, because the debuggee has many custom log messages mixed with normal GDB MI message.

When I run the command "info terminal", it returned: "This GDB does not control a terminal.\n"
So, It looks like gdb does not redirect any terminal.

BTW: I do not have such problem when I use GDB CLI interface to debug Codeblocks.

Anyone has experience the same problem?

I would like the debuggee's own log message goes to its own log window.
(Codeblocks has its own log window, a wxWidgets window to show messages)

Thanks.

Yuanhui Zhang
Code::blocks developer

             reply	other threads:[~2012-04-23  1:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23  1:03 asmwarrior [this message]
2012-04-23  1:13 ` asmwarrior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F94AA91.3060608@gmail.com \
    --to=asmwarrior@gmail.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).