From: Christopher Faylor <cgf@redhat.com>
To: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [rfc] Zap _WIN32 from main.c
Date: Fri, 04 May 2001 14:58:00 -0000 [thread overview]
Message-ID: <20010504175724.A25953@redhat.com> (raw)
In-Reply-To: <3AF2E913.9060902@cygnus.com>
Dunno if you need my approval for this, since it's under a _WIN32 conditional,
but you've got it.
cgf
On Fri, May 04, 2001 at 01:38:27PM -0400, Andrew Cagney wrote:
>Hello,
>
>Per _WIN32 discussion, the attatched zapps the #ifndef _WIN32 from main.c.
>
> Andrew
>2001-05-04 Andrew Cagney <ac131313@redhat.com>
>
> * main.c (captured_main): Delete #ifndef _WIN32 conditional for
> WinGDB.
>
>Index: main.c
>===================================================================
>RCS file: /cvs/src/src/gdb/main.c,v
>retrieving revision 1.9
>diff -p -r1.9 main.c
>*** main.c 2001/04/05 02:02:13 1.9
>--- main.c 2001/05/04 16:56:39
>*************** extern int gdbtk_test (char *);
>*** 706,718 ****
> #endif
> }
>
>- /* The default command loop.
>- The WIN32 Gui calls this main to set up gdb's state, and
>- has its own command loop. */
>- #if !defined _WIN32 || defined __GNUC__
>- /* GUIs generally have their own command loop, mainloop, or
>- whatever. This is a good place to gain control because many
>- error conditions will end up here via longjmp(). */
> #if 0
> /* FIXME: cagney/1999-11-06: The original main loop was like: */
> while (1)
>--- 706,711 ----
>*************** extern int gdbtk_test (char *);
>*** 748,754 ****
> {
> catch_errors (captured_command_loop, 0, "", RETURN_MASK_ALL);
> }
>- #endif
> /* No exit -- exit is through quit_command. */
> }
>
>--- 741,746 ----
--
cgf@cygnus.com Red Hat, Inc.
http://sources.redhat.com/ http://www.redhat.com/
prev parent reply other threads:[~2001-05-04 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 10:38 Andrew Cagney
2001-05-04 14:58 ` Christopher Faylor [this message]
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=20010504175724.A25953@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