Re: Updated: libsigsegv{2}2.8-1

Re: Updated: libsigsegv{2}2.8-1

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Reini Urban on 12/14/2009 10:00 AM:
> Eric Blake's SEH chain corruption fixes for libsigsegv on cygwin are now
> in the official libsigsegv-2.8 release.
> Successfully tested with clisp.
> The DLL revision is bumped from 1 to 2.

I'm curious why you bumped the dll revision when building 2.8.  I don't
see any backwards-incompatible API changes compared to 2.6 that would have
required the bump; am I overlooking something?  But the barn door is open,
now that you have released clisp depending on the new dll revision.  So
I'll now have to rebuild m4 to pick up the new dll version.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAksniMsACgkQ84KuGfSFAYANxgCePGWSv1Rj5OlYEHKom72icY1F
HyAAn1PgYH8AdRMThdd1kAnpOAa3wPyV
=WqmL
-----END PGP SIGNATURE-----

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Updated: libsigsegv{2}2.8-1

[Reini Urban]

Eric Blake schrieb:
> According to Reini Urban on 12/14/2009 10:00 AM:
>> Eric Blake's SEH chain corruption fixes for libsigsegv on cygwin are now
>> in the official libsigsegv-2.8 release.
>> Successfully tested with clisp.
>> The DLL revision is bumped from 1 to 2.
>
> I'm curious why you bumped the dll revision when building 2.8.  I don't
> see any backwards-incompatible API changes compared to 2.6 that would have
> required the bump; am I overlooking something?  But the barn door is open,
> now that you have released clisp depending on the new dll revision.  So
> I'll now have to rebuild m4 to pick up the new dll version.

Me neither. It was not me, it was Bruno Haible, upstream.
But there must be some changes.
LIBSIGSEGV_VERSION_INFO = 2:1:0
2.7 had 2:0:0
And 2.6++ started with 1:0:0
-- 
Reini Urban
http://phpwiki.org/  http://murbreak.at/

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Updated: libsigsegv{2}2.8-1

[Eric Blake]

Reini Urban <rurban <at> x-ray.at> writes:

> >> The DLL revision is bumped from 1 to 2.
> >
> > I'm curious why you bumped the dll revision when building 2.8.  I don't
> > see any backwards-incompatible API changes compared to 2.6 that would have
> > required the bump; am I overlooking something?  But the barn door is open,
> > now that you have released clisp depending on the new dll revision.  So
> > I'll now have to rebuild m4 to pick up the new dll version.
> 
> Me neither. It was not me, it was Bruno Haible, upstream.
> But there must be some changes.
> LIBSIGSEGV_VERSION_INFO = 2:1:0
> 2.7 had 2:0:0
> And 2.6++ started with 1:0:0

According to the libtool versioning scheme, 
http://www.gnu.org/software/libtool/manual/libtool.html#Updating-version-info, 
the change from 2.6 (1:0:0) to 2.7 (2:0:0) requires a dll version bump on the 
surface (the 'current' field changed from 1 to 2 to mark an interface change, 
and the 'age' field reset to 0 meaning that the change is not backwards-
compatible).  But reading the NEWS file, the only documented change was Linux-
specific ("the type 'stackoverflow_context_t' is now typedefed to 'ucontext_t 
*' rather than 'struct sigcontext *'"), so we probably could have survived 
without a dll rev bump.

Meanwhile, the change from 2.7 (2:0:0) to 2.8 (2:1:0) implies complete 
backwards compatibility (the 'revision' field changed from 0 to 1 to reflect 
that code changed to fix bugs, but neither 'current' nor 'age' changed so 
nothing was backwards-incompatible).  And the NEWS appears to back this up, 
with no mention of any interface changes.  But certainly an argument for 
leaving the dll version unchanged.

Just so I'm clear, is the dll version something you manually pick based on the 
libtool version changing, or is it something generated automatically by the 
default build process (either by libtool or by cygport)?  I guess that if the 
version suffix is automatic, based on the fact that the 'current' field changed 
from 1 to 2 between 2.6 and 2.8, then you did the right thing, even if the 
interface change that Bruno based his version bump has no effect on cygwin.

-- 
Eric Blake



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

[ANNOUNCEMENT] Updated: libsigsegv-2.10-1

[Reini Urban]

I included Eric Blake's [PATCH] Avoid polluting cygwin namespace,
also at http://repo.or.cz/w/libsigsegv/ericb.git
Successfully tested with clisp.

See http://cygwin.com/ml/cygwin-apps/2011-05/msg00000.html

It's a small library for handling page faults in user mode.
A page fault occurs when a program tries to access to a region of memory
that is currently not available.
It is mainly required in clisp for generational garbage collection,
m4 also uses it for stack overflow protection.

Canonical homepage:
   http://www.gnu.org/software/libsigsegv/

Canonical download:
   http://ftpmirror.gnu.org/libsigsegv/libsigsegv-2.10.tar.gz

========================================================================

To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system.  Then, run setup and answer all of the questions.

               *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain.com@cygwin.com

If you need more information on unsubscribing, start reading here:

http://sources.redhat.com/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.

-- 
Reini Urban

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple