Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: bje@redhat.com, keiths@cygnus.com, kettenis@science.uva.nl,
	gdb-patches@sources.redhat.com
Subject: Re: [RFC] sigsetjmp/siglongjmp on cygwin
Date: Mon, 13 Aug 2001 15:42:00 -0000	[thread overview]
Message-ID: <3B7857A8.3040708@cygnus.com> (raw)
In-Reply-To: <2593-Mon13Aug2001120249+0300-eliz@is.elta.co.il>

> 
> I suggested to put the work-around into config.site, precisely to
> solve this.  Assuming such a config.site is made part of the core
> Cygwin distribution, whenever sigsetjmp starts working, config.site
> should be updated.  So a user which upgrades to a newer version of
> Cygwin has this issue magically taken care of during the upgrade.


Eli, can you expand a little.  I'm not sure what would happen if a 
current GDB was configured/built on an old cygwin which didn't have the 
config.site file.

	Andrew


      reply	other threads:[~2001-08-13 15:42 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-01 14:01 Keith Seitz
     [not found] ` <s3iae1jjso2.fsf@soliton.wins.uva.nl>
2001-08-01 16:03   ` Keith Seitz
2001-08-01 23:57     ` Eli Zaretskii
2001-08-02 10:25       ` Andrew Cagney
2001-08-02 13:15         ` Mark Kettenis
2001-08-13 14:46           ` Jim Blandy
2001-08-13 15:12             ` Keith Seitz
2001-08-13 15:37               ` Andrew Cagney
2001-08-13 15:43                 ` Keith Seitz
2001-08-13 15:52                   ` Andrew Cagney
2001-08-13 16:27                     ` Keith Seitz
2001-08-13 16:32                       ` Christopher Faylor
     [not found]                         ` <20010813222037.A20589@redhat.com>
2001-08-13 19:40                           ` [RFC] sigsetjmp/siglongjmp on cygwin -- problem tracked down Andrew Cagney
2001-08-13 19:55                             ` Christopher Faylor
2001-08-13 20:10                               ` Daniel Jacobowitz
2001-08-13 20:18                                 ` [RFA] work around sigsetjmp/siglongjmp macro problems Christopher Faylor
2001-08-14  0:06                                   ` Eli Zaretskii
2001-08-14  7:40                                     ` Christopher Faylor
2001-08-14  9:34                                   ` Keith Seitz
2001-08-14 13:01                                     ` Elena Zannoni
2001-08-14 13:08                                       ` Christopher Faylor
2001-08-14 23:52                                         ` Eli Zaretskii
2001-08-14 23:49                                       ` Eli Zaretskii
2001-08-13 17:11                       ` [RFC] sigsetjmp/siglongjmp on cygwin Andrew Cagney
2001-08-13 17:23                         ` Keith Seitz
2001-08-03  1:33         ` Eli Zaretskii
2001-08-10  0:16           ` Andrew Cagney
2001-08-01 16:16   ` Andrew Cagney
2001-08-02 13:51     ` Christopher Faylor
2001-08-10  0:27 ` Andrew Cagney
2001-08-12 15:49   ` Ben Elliston
2001-08-13  2:03     ` Eli Zaretskii
2001-08-13 15:42       ` Andrew Cagney [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=3B7857A8.3040708@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=bje@redhat.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=keiths@cygnus.com \
    --cc=kettenis@science.uva.nl \
    /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