Eric Blake <[EMAIL PROTECTED]> writes:
> OK to apply? Also, should this be modified to print an INFO message warning
> the user if git-version-gen returned UNKNOWN (normally an important warning,
> but one which can be safely ignored in a gnulib-tool testdir)?
I noticed you had pushed this, an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 6/6/2008 7:28 PM:
|
| Can you then please fix the gnulib doc to not be so negative about _setjmp/
| _longjmp? I propose:
|
| A future revision of POSIX later than the 2008/2009 one may drop the
functions
| _setjmp and _lon
Eric Blake wrote:
> I was going off of the POSIX 200x draft copy, where they were given OB
> shading (ie. a future version of POSIX may withdraw support for them).
Sure. But that POSIX 200x draft still describes 'setjmp' as having unspecified
behaviour w.r.t. signal mask. They are calling _setjmp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 6/6/2008 5:53 PM:
|
| Regarding _setjmp and _longjmp you say that they are "obsolete". I disagree
| for two reasons:
I was going off of the POSIX 200x draft copy, where they were given OB
shading (ie. a future version of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 6/6/2008 4:26 PM:
| Eric Blake wrote:
|> * doc/glibc-functions/argz_add.texi (argz_add): Document the argz
|> module and recently fixed cygwin bugs.
|
| Thanks for caring about the documentation!
Except that I missed savi
Eric Blake wrote:
> Meanwhile, I'm committing this (POSIX states
> that the various *setjmp are allowed to be only a macro; but *longjmp must be
> linkable functions):
Thanks for the doc fixes. Most of this symbol / platform presence/absence
matrix was generated automatically. On some macro-like
Eric Blake wrote:
> Should we could create an rpl_abort that works around these two issues?
I wouldn't spend time on this. If you want to print a message
m4 crashed!! Please report this to bug-m4 according to the bug reporting
instructions at http://.
then
- regarding the mingw bug:
Eric Blake wrote:
> On Solaris 8, uc_stack is (IMHO properly) pointing to the primary stack,
> even though the handler is executing on the alternate stack.
That's accidental, IMO.
The only documented use of uc_stack in POSIX:2001 is in the description of
'makecontext', as an input parameter. Its
Eric Blake wrote:
> * doc/glibc-functions/argz_add.texi (argz_add): Document the argz
> module and recently fixed cygwin bugs.
Thanks for caring about the documentation!
Bruno
Eric Blake byu.net> writes:
> >
> > On the other hand, POSIX states for sigaction() that the handler's "third
> > argument can be cast to a pointer to an object of type ucontext_t to refer
to
> > the receiving thread’s context that was interrupted when the signal was
> > delivered."
> |
> |>
I wanted to add a SIGABRT handler to m4, to make it more obvious how to report
internal errors back to the developers. But in the process, I discovered that
Cygwin abort() mistakenly closes stdio before raising SIGABRT, instead of
after:
http://cygwin.com/ml/cygwin/2008-06/msg00122.html
Meanw
Hi Ondřej,
Based on your description, I wrote the following.
Does it solve the problem?
>From 51aca03ab224ad1bf0a5c432403a0131001cda36 Mon Sep 17 00:00:00 2001
From: Jim Meyering <[EMAIL PROTECTED]>
Date: Fri, 6 Jun 2008 18:20:14 +0200
Subject: [PATCH] utimens.c: correct yesterday's kernel bug wo
Jim Meyering meyering.net> writes:
> > For glibc. On cygwin, it looks like all the argz_ functions were added at
> > once, on 2002-06-14. But does this properly test for bugs in the argz_
> > implementation? For example, cygwin argz_add_sep failed to handle empty
string
> > arguments as recen
I got this on cygwin:
copy-acl.c: In function `qcopy_acl':
copy-acl.c:42: warning: unused variable `ret'
So I'm committing the following.
>From 2be9dfe0ecaf831ca87d737ae1069a5a419d7f49 Mon Sep 17 00:00:00 2001
From: Eric Blake <[EMAIL PROTECTED]>
Date: Fri, 6 Jun 2008 08:34:18 -0600
Subject: [PA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Haible wrote:
| 1) Putting the sigsegv.m4 macro from GNU clisp into gnulib,
incorporating
| it into the c-stack module.
please put it into a separate module, because I do not want to pull the
whole c-stack module into clisp when all I wa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Right now, there is a conversation going on in the bug-gnulib list, trying
to determine if XSI supports the ability to distinguish between stack
overflow and programmer error (or even intentional SEGV, such as when
implementing user-space paging on to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 6/6/2008 6:25 AM:
| According to Bruno Haible on 6/6/2008 5:29 AM:
| | The type of the third argument, according to POSIX, is 'void *ucp'.
| Why does
| | it have to be cast? Why is it not directly 'ucontext_t *ucp' (since,
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 6/6/2008 5:29 AM:
| The type of the third argument, according to POSIX, is 'void *ucp'. Why does
| it have to be cast? Why is it not directly 'ucontext_t *ucp' (since, as you
| say, ucontext_t will be defined in )?
I thin
Eric Blake wrote:
> On the other hand, POSIX states for sigaction() that the handler's "third
> argument can be cast to a pointer to an object of type ucontext_t to refer to
> the receiving thread’s context that was interrupted when the signal was
> delivered."
The type of the third argument, ac
19 matches
Mail list logo
