Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com, gdb@sources.redhat.com
Subject: Re: gdb run < file
Date: Fri, 29 Jun 2001 13:53:00 -0000	[thread overview]
Message-ID: <20010629165352.B8545@redhat.com> (raw)
In-Reply-To: <2427-Fri29Jun2001101154+0300-eliz@is.elta.co.il>

On Fri, Jun 29, 2001 at 10:11:54AM +0300, Eli Zaretskii wrote:
>> 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.

Since Cygwin is supposed to emulate Windows, there shouldn't be much
difference between the way UNIX does it and the way Cygwin does it.
All of the shells come from UNIX, anyway.

So, if this is an issue then it must be an issue for UNIX as well.

>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).

win32-nat.c already has a lot of gratutitous differences with the rest
of the "Unix" code in gdb.  I want to be moving in the direction of
making the cygwin parts more unix-like.  So, I would rather that the
redirection follow UNIX rather than attempting to reimplement the
already implemented.

This is, of course, a problem for running a windows-only version of
gdb but I don't know of anyone currently working on that.  Maybe
we need a separate option for when a complete cygwin system isn't
installed.  However, that would be secondary to getting something
working with /bin/sh or whatever.

cgf


  reply	other threads:[~2001-06-29 13:53 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
2001-06-29 13:53         ` Christopher Faylor [this message]
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=20010629165352.B8545@redhat.com \
    --to=cgf@redhat.com \
    --cc=cygwin@cygwin.com \
    --cc=gdb@sources.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