Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] run > file for win32
Date: Sat, 16 Feb 2002 02:03:00 -0000	[thread overview]
Message-ID: <20020216023944.GA22542@redhat.com> (raw)

I've just adapted some patches from Tak Ota to win32-nat.c.

Tak's patch didn't seem to be complete but the concept was so nice that
I took some time in the last few days and finished things.

The result is that you can use shell meta characters in gdb now, so
things like 'run < foo > bar' now work.

Since this is a departure from previous behavior, I turned this is off
by default.  I added a 'set shell' command to control whether it is used
or not.

Hmm.  I forgot to document this, didn't I?  I'll submit that patch later.

Thanks you for your contribution, Tak!  I've wanted this in the windows
version of gdb for a long time.

cgf

2002-02-15  Christopher Faylor  <cgf@redhat.com>
            Tak Ota <Takaaki.Ota@am.sony.com>

	* win32-nat.c (get_image_name): New function.
	(handle_load_dll): Use get_image_name function.
	(get_child_debug_event): Avoid registering debug events until possibly
	execed process is started.
	(child_create_inferior): Allow invocation via shell so that command
	line redirection, etc.  works ok.
	(_initialize_inftarg): Add new command: "set shell" to control whether
	a shell is used to start a process.


             reply	other threads:[~2002-02-16 10:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-16  2:03 Christopher Faylor [this message]
2002-02-20  1:58 ` Pierre Muller
2002-02-20  8:11   ` Christopher Faylor
2002-02-20  8:41     ` Pierre Muller
2002-02-20  8:58       ` Christopher Faylor
2002-02-20 10:42         ` 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=20020216023944.GA22542@redhat.com \
    --to=cgf@redhat.com \
    --cc=gdb-patches@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