From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: <gdb-patches@sourceware.org>
Subject: RE: [RFC] win32-nat.c 'set new-console' and interruption
Date: Mon, 23 Jun 2008 07:40:00 -0000 [thread overview]
Message-ID: <000101c8d501$3882d100$a9887300$@u-strasbg.fr> (raw)
In-Reply-To: <20080622031804.GB4200@ednor.casa.cgf.cx>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Christopher Faylor
> Envoyé : Sunday, June 22, 2008 5:18 AM
> À : gdb-patches@sourceware.org; Pierre Muller
> Objet : Re: [RFC] win32-nat.c 'set new-console' and interruption
>
> On Sat, Jun 21, 2008 at 08:36:48PM +0200, Corinna Vinschen wrote:
> >On Jun 21 13:21, Daniel Jacobowitz wrote:
> >> On Sat, Jun 21, 2008 at 01:05:21PM -0400, Christopher Faylor wrote:
> >> > 2. What is newconsole good for? I never use it and wonder if it
> >> > shouldn't just be nuked. My usual refrain applies here: Is there
> >> > anything similar in regular gdb?
> >>
> >> I believe this is similar to "set inferior-tty", though I'm not sure
> >> exactly what the Windows version does.
> >
> >It starts the inferior in a new console window, different from the
> >console window GDB is running in. It's quite similar to what "set
> >inferior-tty" is for.
>
> So it actually is useful and used then?
Under the Free Pascal IDE (project on which I
worked for quite some time) I placed the
new-console as an equivalent of the 'set tty'
and it is much easier to have the debuggee to run in a separate console
that to do all the switching back and forth of all console parameters.
I run gdb mainly in that mode for cygwin,
but the lack of capability of interrupting the
debuggee from the GDB console was annoying me for a long time already!
I will resend a new patch proposal that complies with
the lowercase coding standard rule shortly.
Pierre Muller
Pascal language support maintainer for GDB
next prev parent reply other threads:[~2008-06-23 7:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 17:05 Pierre Muller
2008-06-21 18:37 ` Christopher Faylor
2008-06-22 3:17 ` Daniel Jacobowitz
2008-06-22 3:18 ` Corinna Vinschen
2008-06-23 1:04 ` Christopher Faylor
2008-06-23 1:10 ` Corinna Vinschen
2008-06-23 7:40 ` Pierre Muller [this message]
2008-06-23 12:00 ` Christopher Faylor
2008-06-23 16:05 ` Pierre Muller
2008-06-23 17:00 ` Pedro Alves
2008-06-23 17:25 ` Pierre Muller
2008-06-23 18:03 ` Christopher Faylor
2008-06-23 19:24 ` Pedro Alves
2008-06-23 20:33 ` Pierre Muller
2008-06-23 21:06 ` Joel Brobecker
2008-06-24 6:33 ` Christopher Faylor
2008-06-24 13:36 ` [RFC-v3] " Pierre Muller
2008-06-24 2:33 ` [RFC] " Christopher Faylor
2008-06-24 13:54 ` Pedro Alves
2008-06-24 18:29 ` Christopher Faylor
2008-06-22 9:00 ` Christopher Faylor
2008-06-23 8:52 ` [RFC v2] " Pierre Muller
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='000101c8d501$3882d100$a9887300$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=gdb-patches@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