Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: cygwin@cygwin.com, gdb@sources.redhat.com
Cc: Takaaki.Ota@am.sony.com, cygwin@cygwin.com,
	gdb@sources.redhat.com, jimb@redhat.com
Subject: Re: gdb run < file
Date: Fri, 29 Jun 2001 00:20:00 -0000	[thread overview]
Message-ID: <2427-Fri29Jun2001101154+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <20010628220602.A3596@redhat.com>

> Date: Thu, 28 Jun 2001 22:06:02 -0400
> From: Christopher Faylor <cgf@redhat.com>
> 
> I'm sorry but I don't think that this is the correct way to deal with
> this.  I think that gdb normally handles things like redirection and
> globbing by starting inferior processes via the user's shell.  Then it
> uses some kind of "follow fork" method to notice when the process is
> finally started.

I don't know anything about Windows debugging interface, but it might
be that putting a shell between the debugger and the debuggee breaks
something.

Going through the shell also has the limitation that you buy whatever
idiosyncrasies there are in that shell.  Unlike on Unix, where the
redirection behavior is quite similar between the shells, on Windows
there's a very wide disagreement.  (We are fed up with that nuisance
in the Emacs-land.)  So I think there's a lot of sense in having a
unified, predictable redirection support inside GDB that doesn't
depend on the queer shell the user happens to have.

FWIW, the DJGPP port of GDB does something very similar to the patch
we discuss here (except that it also has to flip redirections every
time the execution thread jumps from the debugger to the debuggee).
See go32-nat.c (the actual implementation of the redirection routines
is in the DJGPP debug support library).


  parent reply	other threads:[~2001-06-29  0:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010626.234402.21347360.Takaaki.Ota@am.sony.com>
     [not found] ` <20010627025036.B20160@redhat.com>
     [not found]   ` <20010627.235700.01365880.Takaaki.Ota@am.sony.com>
2001-06-28 19:05     ` Christopher Faylor
2001-06-28 21:45       ` Tak Ota
2001-06-29  0:20       ` Eli Zaretskii [this message]
2001-06-29 13:53         ` Christopher Faylor
2001-06-29 13:55           ` Christopher Faylor
2001-06-29 23:36           ` Eli Zaretskii
2001-06-30 10:25             ` Christopher Faylor
2001-06-30 17:23               ` Tak Ota
2001-06-30 22:20                 ` Tak Ota
2001-07-01  1:20                 ` Eli Zaretskii

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=2427-Fri29Jun2001101154+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=Takaaki.Ota@am.sony.com \
    --cc=cygwin@cygwin.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@redhat.com \
    /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