clisp-devel — closed list for developers and testers

xmutex vs xlock

[Compro P. <com...@gm...>]

I don't see the point in having "xmutex_t" defined as "xlock_t" and
"xmutex_raw_t" defined as "pthread_mutex_t". I mean how is xmutex_t
related to xmutex_raw_t ? I see it as a redundant definition which
makes the real definition look clumsy.

Compro

Re: libffcall and selinux

[Bruno H. <br...@cl...>]

Hi Don,

> Just looking at 
>  getsebool -a | grep selinuxuser
> I see
>  selinuxuser_execheap --> off
> which is what causes the AVC denial in configuring ffcall.
> (I verified that by turning it on and redoing config.)
> 
> This is described as follows at
>  https://mgrepl.fedorapeople.org/man_selinux/Fedora18/user.html
> 
>  If you want to allow unconfined executables to make their heap memory
>  executable. Doing this is a really bad idea. Probably indicates a
>  badly coded executable, but could indicate an attack. This executable
>  should be reported in bugzilla, you must turn on the
>  selinuxuser_execheap boolean.
>  setsebool -P selinuxuser_execheap 1
> 
> However, getsebool also shows
>  selinuxuser_execstack --> on
> 
>  If you want to allow unconfined executables to make their stack
>  executable. This should never, ever be necessary. Probably indicates
>  a badly coded executable, but could indicate an attack. This
>  executable should be reported in bugzilla, you must turn on the
>  selinuxuser_execstack boolean.
>  setsebool -P selinuxuser_execstack 1

Thanks for these pointers. I installed a RHEL 6 VM, then looked at how
these flags influence the libffcall configure tests, and modified libffcall
to bypass these configure tests in case of SELinux. Since the results
are dependent on flags that can change at runtime, the code better assumes
the worst possible result.

Bruno

Re: clisp: New frame type CHANDLER.

[Sam S. <sd...@gn...>]

Hi Bruno,

> * Bruno Haible <oe...@py...t> [2017-06-02 19:17:49 +0200]:
>
>> 2. HANDLER_FRAME is a substring of CHANDLER_FRAME (thus search
>> problems).
>
> 'object' is a substring of 'gcv_object_t', and so on.

This sucks too.
I would rename `object' to `unsafe_object_t'.

> Emacs and grep both have ways to search for identifiers, regardless of
> other identifiers that may contain the search term as a substring.

Simple things should be easy.
Typing [^_]HANDLER_FRAME (and making sure that "[]" are not special in
the tool chain) is harder than typing L_HANDLER_FRAME.
It also requires knowledge that the only other HANDLER_FRAME is
C_HANDLER_FRAME.
L_HANDLER_FRAME also lends itself to automatic search term extraction
easier, e.g., Emacs command "recursively search all project directories
for symbol at point".

However, this is not important enough for an extended discussion.

Have a great weekend!

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net
http://www.memritv.org http://memri.org https://jihadwatch.org
Every day above ground is a good day.

misnomers

[Bruno H. <br...@cl...>]

Hi all,

There are a couple of wrong terms in the source code:

* NESTED_IBLOCK/ITAGBODY_frame_info, nest_fun, nest_env:
  I'll rename "nested" to "captured".
  Because what it does is to move values from the stack
  (where they will disappear when the stack frame is unwound)
  to other locations (where they cannot disappear, other
  than being GCed).

* How to call the result of capturing a stack frame?
  It's a simple-vector consisting of binding cells.
  The previous term "closure" is wrong (see [1]).
  I'm hesitating between
    - "a capture" - because of the verb "capture" above,
      but still a misnomer [2],
    - "a prison" - because it's a container for *cell*s,
      and contains *capture*d values.

Opinions? Objections?

Bruno

[1] https://en.wikipedia.org/wiki/Closure_(computer_programming)
[2] http://wordnetweb.princeton.edu/perl/webwn?s=capture&sub=Search+WordNet&o2=&o0=1&o8=1&o1=1&o7=&o5=&o9=&o6=&o3=&o4=&h=

Re: clisp: New frame type CHANDLER.

[Bruno H. <br...@cl...>]

Hi Sam,

> Problems:
> 
> 1. CHANDLER is a common English word.

Although it's quite common in the Lisp community to reuse English words
(think of "Bigloo"), I agree it's better with an extra underscore.

> 2. HANDLER_FRAME is a substring of CHANDLER_FRAME (this search
> problems).

'object' is a substring of 'gcv_object_t', and so on. Emacs and grep
both have ways to search for identifiers, regardless of other identifiers
that may contain the search term as a substring.

> Proposal:
> 
> 2. Rename CHANDLER_FRAME to C_HANDLER_FRAME

Done.

Bruno

Re: [clisp:clisp] New commit [729b7f] by Vladimir Tzankov

[<Joe...@t-...>]

Hi,

That change is incorrect (the old test was incorrect too).

-    #if defined(UNIX_LINUX) || defined(UNIX_FREEBSD) || (defined(UNIX_MACOSX) && (__GNUC__ == 4) && ((__GNUC_MINOR__ >= 5)))
+    #if defined(UNIX_LINUX) || defined(UNIX_FREEBSD) || (defined(UNIX_MACOSX) && (defined(__clang__) || ((__GNUC__ >= 4) && (__GNUC_MINOR__ >= 5))))

The old one did not test correctly for GCC >= 4.5 (supposing that was intended).
 For example, think about gcc v 5.2.
The new one will produce different results for gcc 5.2 and 5.7. This is certainly unwanted.

The GCC manual shows examples about how to test for >= a specific version
 (whether x*100+y is a good trick is debatable).
https://gcc.gnu.org/onlinedocs/cpp/Common-Predefined-Macros.html

Regards,
	Jörg

clisp-cvs Digest, Vol 77, Issue 6

[<cli...@li...>]

Send clisp-cvs mailing list submissions to
	cli...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/clisp-cvs
or, via email, send a message with subject or body 'help' to
	cli...@li...

You can reach the person managing the list at
	cli...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of clisp-cvs digest..."


CLISP CVS commits for today

Today's Topics:

   1. clisp: Don't publish impnotes.html for the moment.
      (cli...@li...)
   2. clisp: Document the -nextgc-factor option.
      (cli...@li...)
   3. clisp: doc: Reference kernel.org, not linuxfoundation.org.
      (cli...@li...)
   4. clisp: doc: Regenerate. (cli...@li...)
   5. clisp: use __thread with clang on UNIX_MACOSX
      (cli...@li...)
   6. clisp: fix __GNUC__ version check
      (cli...@li...)


----------------------------------------------------------------------

Message: 1
Date: Tue, 30 May 2017 17:51:34 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: Don't publish impnotes.html for the moment.
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/227cc7471555
changeset: 15921:227cc7471555c4b424d2e7313b7a24365997db91
user:      Bruno Haible <br...@cl...>
date:      2017-05-30 19:31:22 +0200
description:
Don't publish impnotes.html for the moment.

diffstat:

 doc/Makefile  |  2 +-
 src/ChangeLog |  5 +++++
 2 files changed, 6 insertions(+), 1 deletions(-)



------------------------------

Message: 2
Date: Tue, 30 May 2017 17:51:35 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: Document the -nextgc-factor option.
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/30d5d1f3f739
changeset: 15922:30d5d1f3f739bb7528793f7c9a193f10fecf31d3
user:      Bruno Haible <br...@cl...>
date:      2017-05-30 19:38:51 +0200
description:
Document the -nextgc-factor option.

diffstat:

 doc/impbyte.xml |  24 ++++++++++++++++++++++++
 1 files changed, 24 insertions(+), 0 deletions(-)



------------------------------

Message: 3
Date: Tue, 30 May 2017 17:51:36 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: doc: Reference kernel.org, not linuxfoundation.org.
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/8ba9d4f9469f
changeset: 15923:8ba9d4f9469f326a9e1cc147f4d958e251b30be3
user:      Bruno Haible <br...@cl...>
date:      2017-05-30 19:45:22 +0200
description:
doc: Reference kernel.org, not linuxfoundation.org.

diffstat:

 doc/cl-ent.xml |  2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)



------------------------------

Message: 4
Date: Tue, 30 May 2017 17:51:37 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: doc: Regenerate.
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/01fb2db8cbdb
changeset: 15924:01fb2db8cbdbba51f8fd2b3c4588f4fe2f6ad05e
user:      Bruno Haible <br...@cl...>
date:      2017-05-30 19:50:49 +0200
description:
doc: Regenerate.

diffstat:

 doc/_clisp-link.1    |    21 +-
 doc/_clisp-link.html |    45 +-
 doc/_clisp.1         |   130 +-
 doc/_clisp.html      |   250 +-
 doc/impnotes.html    |  7004 +++++++++++++++++++++++--------------------------
 5 files changed, 3486 insertions(+), 3964 deletions(-)



------------------------------

Message: 5
Date: Tue, 30 May 2017 22:15:16 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: use __thread with clang on UNIX_MACOSX
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/729b7fc3e941
changeset: 15925:729b7fc3e9412dc3b1b645a60bd031b91fc13411
user:      Vladimir Tzankov <vtz...@gm...>
date:      2017-05-31 01:14:59 +0300
description:
use __thread with clang on UNIX_MACOSX

diffstat:

 src/ChangeLog  |  4 ++++
 src/lispbibl.d |  2 +-
 2 files changed, 5 insertions(+), 1 deletions(-)



------------------------------

Message: 6
Date: Wed, 31 May 2017 05:15:17 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: fix __GNUC__ version check
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/781cf2b55fc8
changeset: 15926:781cf2b55fc8fe17009f27cb51d7ce2f562b596f
user:      Vladimir Tzankov <vtz...@gm...>
date:      2017-05-31 08:15:05 +0300
description:
fix __GNUC__ version check

diffstat:

 src/lispbibl.d |  2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)



------------------------------

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

------------------------------

Subject: Digest Footer

_______________________________________________
clisp-cvs mailing list
cli...@li...
https://lists.sourceforge.net/lists/listinfo/clisp-cvs


------------------------------

End of clisp-cvs Digest, Vol 77, Issue 6
****************************************

Re: __GNUC__ and __GNUC_MINOR__

[Vladimir T. <vtz...@gm...>]

On Wed, May 31, 2017 at 1:52 AM, Bruno Haible <br...@cl...> wrote:

> In this conditional expression:
> ((__GNUC__ >= 4) && (__GNUC_MINOR__ >= 5))
> the conditional for GCC looks odd: it
>  - includes versions 4.5, 4.6, 4.7, 4.8, 4.9
>  - but excludes versions 5.4, 6.3, 7.1
> which is probably not what you meant since GCC 5.4 is a successor of 4.9.
>
> The usual way to write conditions like this is
>   (((__GNUC__ == 4) && (__GNUC_MINOR__ >= 5)) || (__GNUC__ > 4))
> or - not my preferred coding style -
>   (__GNUC__ + (__GNUC_MINOR__ >= 5) > 4)
>

Oops, my bad! Fixed.



> Note that this doesn't help with clang on Mac OS X, since it defines
> __GNUC__ = 4 and __GNUC_MINOR__ = 2.


Yes,  that's the reason I added explicit check for __clang__.

__GNUC__ and __GNUC_MINOR__

[Bruno H. <br...@cl...>]

Hi Vladimir,

In this conditional expression:
((__GNUC__ >= 4) && (__GNUC_MINOR__ >= 5))
the conditional for GCC looks odd: it
 - includes versions 4.5, 4.6, 4.7, 4.8, 4.9
 - but excludes versions 5.4, 6.3, 7.1
which is probably not what you meant since GCC 5.4 is a successor of 4.9.

The usual way to write conditions like this is
  (((__GNUC__ == 4) && (__GNUC_MINOR__ >= 5)) || (__GNUC__ > 4))
or - not my preferred coding style -
  (__GNUC__ + (__GNUC_MINOR__ >= 5) > 4)

Note that this doesn't help with clang on Mac OS X, since it defines
__GNUC__ = 4 and __GNUC_MINOR__ = 2.

Bruno

Re: libffcall and selinux

[Bruno H. <br...@cl...>]

Hi Don,

>  > > However, getsebool also shows
>  > >  selinuxuser_execstack --> on
>  > > 
>  > >  If you want to allow unconfined executables to make their stack
>  > >  executable. This should never, ever be necessary. Probably indicates
>  > >  a badly coded executable, but could indicate an attack. This
>  > >  executable should be reported in bugzilla, you must turn on the
>  > >  selinuxuser_execstack boolean.
>  > >  setsebool -P selinuxuser_execstack 1
>  > 
>  > This looks like the one that may be related to libffcall.
> 
> No, libffcall was triggering execheap. ...
> I've not yet seen any execstack complaints.

Oh, this is more complex than I thought.

> So as far as I know so far, current clisp has no issues with selinux
> on latest fedora.

Yup. I keep this issue on my radar, but won't do something about it
unless someone reports a real problem.

Bruno

Re: TRUENAME on Windows

[Sam S. <sd...@gn...>]

> * Reini Urban <ervav.heona@tznvy.pbz> [2017-05-30 11:35:47 +0200]:
>
> windows still has the TRUENAME: Filename for #<OUTPUT UNBUFFERED
> FILE-STREAM CHARACTER> is unknown
> problem:

I have no access to a windows box (and I cannot figure out how to use
the links you sent, sorry).
Could you please tell me which specific test(s?) fail?

Thanks!

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net https://ffii.org
http://no2bds.org http://iris.org.il http://islamexposedonline.com
Life sucks, but the alternative is even worse.

Re: errors on streams

[Sam S. <sd...@gn...>]

> * Don Cohen <qba...@vf...3-vap.pbz> [2017-05-30 19:35:56 +0000]:
>
> Bruno Haible writes:
>  > Of course you should never build any package as 'root'.
>
> An yet there are features that can only be used as root, so if you
> want to test them you have to test as root.

Indeed.
Still, you never build the package as root.
When you built it, you can _test_ specific features as root though.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://memri.org
http://americancensorship.org https://jihadwatch.org http://no2bds.org
The biggest childhood mistake is thinking that being an adult is fun.

Re: clisp: New frame type CHANDLER.

[Sam S. <sd...@gn...>]

Hi Bruno,

Problems:

1. CHANDLER is a common English word.
2. HANDLER_FRAME is a substring of CHANDLER_FRAME (this search
problems).

Proposal:

1. Rename HANDLER_FRAME to L_HANDLER_FRAME
2. Rename CHANDLER_FRAME to C_HANDLER_FRAME

Thank you!

> *  <pyv...@yv...g> [2017-05-27 19:22:08 +0000]:
>
> details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/6a5acbe357f8
> changeset: 15912:6a5acbe357f8a5d97dec313934d4f072935cb9a1
> user:      Bruno Haible <br...@cl...>
> date:      2017-05-27 18:42:36 +0200
> description:
> New frame type CHANDLER.
>
> diffstat:
>
>  src/ChangeLog         |   28 +++++++++++
>  src/eval.d            |   11 ++--
>  src/io.d              |    9 ++-
>  src/lispbibl.d        |  122 ++++++++++++++++++++++++++-----------------------
>  src/pathname.d        |   14 ++--
>  src/spvw_garcol.d     |    9 ++-
>  src/spvw_garcol_old.d |    9 ++-
>  src/spvw_update.d     |    9 ++-
>  src/stream.d          |   30 ++++++------
>  9 files changed, 143 insertions(+), 98 deletions(-)
>
>

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://jij.org
http://thereligionofpeace.com http://memri.org http://honestreporting.com
If you want to shoot yourself, it is YOUR responsibility to wear armor.

Re: newcomers

[Sam S. <sd...@gn...>]

Hi Bruno,

> * Bruno Haible <oe...@py...t> [2017-05-27 23:27:39 +0200]:
>
> Possibly every module should be accompanied with unit tests?

Most modules already are.
See "make mod-check".

>> Normal users are also affected - people try something and submit bug
>> reports without reading http://www.clisp.org/impnotes/clisp.html#bugs and
>> following conversation is about 'clisp --version', build options, etc.
>> Probably having binary releases is the 'good enough' solution for this.
>
> I don't think one can do anything about this, other than to remind the
> users what information to provide.
> Different OSes have different support for mmap, __thread, system calls, etc.
> - therefore invariably the builds on different OSes will end up using
> different code paths.
>
> Or should we hook into 'apport', so that the details get collected
> automatically?

'clisp --version' is our apport.
It is supposed to print _everything_ you ever want to know.
If you find yourself asking for a bug reporter for extra info, you
should incorporate it into "clisp --version".
If you feel that its output is growing too huge, you can make "clisp -v"
print "short version" and "clisp --version" the long one.
And then you will find yourself telling every other bug reporter to
submit "clisp --version" in addition to "clisp -v". :-)

PS. I think your answer will be:
    "clisp --version" cannot print the whole "config.log"  :-)

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://mideasttruth.com
http://islamexposedonline.com http://www.memritv.org http://iris.org.il
MS Windows vs IBM OS/2: Why marketing matters more than technology...

Re: errors on streams

[<don...@is...>]

Bruno Haible writes:
 > Of course you should never build any package as 'root'.

An yet there are features that can only be used as root, so if you
want to test them you have to test as root.

 > But what are the "permission denied errors from streams" that you
 > mention?

(WITH-OPEN-FILE (COPY S) (STREAMP COPY))
[OS-FILE-ERROR]: OS-FILE-ERROR(13): Permission denied

(STREAMP (SETQ S (MAKE-STREAM :INPUT)))
EQL-OK: T
(OR (NOT (SEARCH "#P" (PRIN1-TO-STRING S))) (PATHNAMEP (TRUENAME S)))
EQL-OK: T
(HANDLER-CASE (WRITE-LINE "foo" S) (STREAM-ERROR (C) (PRINC-ERROR C) T))
[SIMPLE-STREAM-ERROR]: WRITE-CHAR on #1=#<INPUT UNBUFFERED FILE-STREAM CHARACTER #P"/dev/fd/0" @1> is illegal

EQL-OK: T
(WITH-OPEN-FILE (COPY S) (STREAMP COPY))
[OS-FILE-ERROR]: OS-FILE-ERROR(13): Permission denied

whereas above returns T as root

in this case:
[7]> s
#<INPUT UNBUFFERED FILE-STREAM CHARACTER #P"/dev/fd/0" @1>


(STREAMP (SETQ S (MAKE-STREAM :ERROR)))
EQL-OK: T
(OR (NOT (SEARCH "#P" (PRIN1-TO-STRING S))) (PATHNAMEP (TRUENAME S)))
EQL-OK: T
(WRITE-LINE "foo" S)
foo
EQUAL-OK: "foo"
(LET ((*REOPEN-OPEN-FILE* NIL)) (WITH-OPEN-FILE (COPY S :DIRECTION :OUTPUT) (STREAMP COPY)))
[OS-FILE-ERROR]: OS-FILE-ERROR(13): Permission denied

returns T as root

Re: libffcall and selinux

[<don...@is...>]

 > > However, getsebool also shows
 > >  selinuxuser_execstack --> on
 > > 
 > >  If you want to allow unconfined executables to make their stack
 > >  executable. This should never, ever be necessary. Probably indicates
 > >  a badly coded executable, but could indicate an attack. This
 > >  executable should be reported in bugzilla, you must turn on the
 > >  selinuxuser_execstack boolean.
 > >  setsebool -P selinuxuser_execstack 1
 > 
 > This looks like the one that may be related to libffcall.

No, libffcall was triggering execheap.  It still does in the
conftest, but that qualifies as intended behavior.

I've not yet seen any execstack complaints.

 > If you can go on with experiments, the better.
 > If not, I will pursue this avenue further.

I should probably read more about selinux anyway.

 > >  If you want to allow all unconfined executables to use libraries
 > >  requiring text relocation that are not labeled textrel_shlib_t, you
 > >  must turn on the selinuxuser_execmod boolean.
 > >  setsebool -P selinuxuser_execmod 1 
 > 
 > clisp doesn't use this feature (it's x86 specific, and the Solaris linker
 > has produced errors for this situation already for years, IIRC).

I've not seen any complaints about this one either.

So as far as I know so far, current clisp has no issues with selinux
on latest fedora.
(Plenty of other things do, though.)

Re: TRUENAME on Windows

[Bruno H. <br...@cl...>]

Hi Reini,

Please routinely set the mail subject. This makes it easier to manage the mails
and to peruse the archives.

> windows still has the TRUENAME: Filename for #<OUTPUT UNBUFFERED FILE-STREAM CHARACTER> is unknown
> problem:
> 
> https://ci.appveyor.com/project/rurban/clisp/history

Can you describe this issue for Sam (who was the last one to work on TRUENAME
for streams), please?

I personally won't look at the Windows build soon; the various Unix builds
have higher priority for me.

Bruno

Re: ci results

[Bruno H. <br...@cl...>]

Hi Reini,

Please routinely set the mail subject. This makes it easier to manage the mails
and to peruse the archives.

> With "Fix GC bug that affects some stream types (regression from 2004-04-28)"
> the first time my linux smokers pass:
> 
> https://travis-ci.org/rurban/clisp/builds

Great! Kudos to Vladimir, again.

Bruno

Re: errors on streams

[Bruno H. <br...@cl...>]

Don Cohen wrote:
> Also make check only shows the two permission denied
> errors from streams (the segmentation fault is fixed).
> 
> Also no AVCs, this is still with
>  selinuxuser_execheap --> off
>  selinuxuser_execmod --> off
>  selinuxuser_execstack --> off
> (the last two changed from default settings)
> ...
> I'm now assuming you're supposed to build clisp as a non-root user

Of course you should never build any package as 'root'.
But what are the "permission denied errors from streams" that you mention?

Bruno

Re: hg pull

[Bruno H. <br...@cl...>]

>  > Always use "hg pull --update".
> 
> That also did not work for me.
> I finally gave up and re cloned in order to get latest updates,
> inc. GC fix.

I was in a similar situation, after "hgview" was showing that the
'default' branch had two heads. To get rid of the unused unnamed
branch, I also ended up re-cloning.

Bruno

Re: libffcall and selinux

[Bruno H. <br...@cl...>]

Hi Don,

>  > Yes, it would be useful to enable SELinux checks (at least those
>  > that smell like related to "restricted mprotect" or like "write xor
>  > execute" or similar, and see how clisp behaves with these checks
>  > enabled.
> ...
> However, getsebool also shows
>  selinuxuser_execstack --> on
> 
>  If you want to allow unconfined executables to make their stack
>  executable. This should never, ever be necessary. Probably indicates
>  a badly coded executable, but could indicate an attack. This
>  executable should be reported in bugzilla, you must turn on the
>  selinuxuser_execstack boolean.
>  setsebool -P selinuxuser_execstack 1

This looks like the one that may be related to libffcall.

If you can go on with experiments, the better.
If not, I will pursue this avenue further.

>  selinuxuser_execmod --> on
> 
>  If you want to allow all unconfined executables to use libraries
>  requiring text relocation that are not labeled textrel_shlib_t, you
>  must turn on the selinuxuser_execmod boolean.
>  setsebool -P selinuxuser_execmod 1 

clisp doesn't use this feature (it's x86 specific, and the Solaris linker
has produced errors for this situation already for years, IIRC).

Bruno

Re: new command-line option -nextgc-factor

[Bruno H. <br...@cl...>]

Hi Don,

>  > I don't want to document this option, because the default GC frequency
>  > is completely sufficient for the average user.
> 
> You do have a section on debugging (also gc) in impnotes.
> Why not include what you wrote in this message there?

Thanks for the suggestion. Done.

> And in the doc for command line arguments refer to
> the appropriate section of impnotes.

No. I don't want to make this command-line option too widely known.

Bruno

Re: new command-line option -nextgc-factor

[<don...@is...>]

Bruno Haible writes:
 > Don Cohen wrote:
 > > I just did hg pull and I don't see this new option.
 > > Am I using the right repository?  Is there a delay?
 > > 
 > >  [don@localhost clisp]$ hg pull
 > 
 > Always use "hg pull --update".

That also did not work for me.
I finally gave up and re cloned in order to get latest updates,
inc. GC fix.

Now the build seems to work:
 unlike last time I have no problem with the new po files
Also make check only shows the two permission denied
errors from streams (the segmentation fault is fixed).

Also no AVCs, this is still with
 selinuxuser_execheap --> off
 selinuxuser_execmod --> off
 selinuxuser_execstack --> off
(the last two changed from default settings)
Also this is with the listener on port 9090 turned off:
 # systemctl status cockpit.socket 
 cockpit.socket - Cockpit Web Service Socket
   Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; enabled; vendor preset: enabled)
   Active: inactive (dead) since Thu 2017-05-25 12:09:22 PDT; 4 days ago
     Docs: man:cockpit-ws(8)
   Listen: [::]:9090 (Stream)
 ...

I'm now assuming you're supposed to build clisp as a non-root user
(I recall getting complaints when building as root), so it seems to 
me that the make check tests ought to assume you're running without
root permissions.
Or possibly accept as a result to certain tests either what you 
should get if you don't have permission or what you should get if
you do.

And perhaps the test that uses port 9090 could try a few other ports
if that one turns out to be in use.

Can you think of any other tests you'd like to try on
this Fedora-Server-dvd-x86_64-25-1.3 VM ?

clisp-cvs Digest, Vol 77, Issue 5

[<cli...@li...>]

Send clisp-cvs mailing list submissions to
	cli...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/clisp-cvs
or, via email, send a message with subject or body 'help' to
	cli...@li...

You can reach the person managing the list at
	cli...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of clisp-cvs digest..."


CLISP CVS commits for today

Today's Topics:

   1. clisp: doc: Add details about how to use the bug tracker.
      (cli...@li...)
   2. clisp: Fix GC bug that affects some stream types (regression
      fro... (cli...@li...)


----------------------------------------------------------------------

Message: 1
Date: Mon, 29 May 2017 23:33:21 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: doc: Add details about how to use the bug tracker.
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/74f6fd4c7e87
changeset: 15919:74f6fd4c7e8798e3c5e07c872b8208b36eea7ab9
user:      Bruno Haible <br...@cl...>
date:      2017-05-30 01:33:01 +0200
description:
doc: Add details about how to use the bug tracker.

diffstat:

 doc/clisp.xml.in |  7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)



------------------------------

Message: 2
Date: Tue, 30 May 2017 01:17:40 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: Fix GC bug that affects some stream types (regression
	fro...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/f89594b12931
changeset: 15920:f89594b129317e79fde6d32e20248e8b2e9524a4
user:      Bruno Haible <br...@cl...>
date:      2017-05-30 02:26:28 +0200
description:
Fix GC bug that affects some stream types (regression from 2004-04-28).

diffstat:

 src/ChangeLog        |  14 ++++++++++++++
 src/lispbibl.d       |  21 ++-------------------
 src/spvw_typealloc.d |  10 ++++------
 3 files changed, 20 insertions(+), 25 deletions(-)



------------------------------

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

------------------------------

Subject: Digest Footer

_______________________________________________
clisp-cvs mailing list
cli...@li...
https://lists.sourceforge.net/lists/listinfo/clisp-cvs


------------------------------

End of clisp-cvs Digest, Vol 77, Issue 5
****************************************

Re: new command-line option -nextgc-factor

[Reini U. <rei...@gm...>]

With "Fix GC bug that affects some stream types (regression from 2004-04-28)"
the first time my linux smokers pass:

https://travis-ci.org/rurban/clisp/builds

windows still has the TRUENAME: Filename for #<OUTPUT UNBUFFERED FILE-STREAM CHARACTER> is unknown
problem:

https://ci.appveyor.com/project/rurban/clisp/history

Reini Urban
ru...@cp...



> On May 28, 2017, at 2:19 PM, Bruno Haible <br...@cl...> wrote:
> 
> Hi all,
> 
> For debugging GC problems, I have added a new option -nextgc-factor.
> It is a factor that gets applied to the amount of space that can be
> consumed before the next GC is triggered.
> 
> Setting it to large values can inhibit GC for a long time:
> 
> $ ./lisp.run -q -M lispinit.mem -nextgc-factor 1e9
> [1]> (time (setq a (make-array 1000000) b nil))
> Real time: 0.038371 sec.
> Run time: 0.04 sec.
> Space: 8000016 Bytes
> NIL
> [2]> (room)
> 
> Number of garbage collections:                0
> Bytes freed by GC:                            0
> Time spent in GC:                           0.0 sec
> Bytes permanently allocated:            158,480
> Bytes currently in use:              11,107,792
> Bytes available until next GC: 1,536,935,991,966,080
> 11107792 ;
> 1536935991966080 ;
> 158480 ;
> 0 ;
> 0 ;
> 0
> 
> Setting it to small values can make GCs much more frequent:
> 
> $ ./lisp.run -q -M lispinit.mem -nextgc-factor 0.001
> [1]> (room)
> 
> Number of garbage collections:               16
> Bytes freed by GC:                       44,648
> Time spent in GC:                         1.112 sec
> Bytes permanently allocated:            158,480
> Bytes currently in use:               3,056,200
> Bytes available until next GC:               71
> 3056200 ;
> 71 ;
> 158480 ;
> 16 ;
> 44648 ;
> 1112000
> [2]> (time (setq a (make-list 1000) b nil))
> Real time: 0.687479 sec.
> Run time: 0.688 sec.
> Space: 16000 Bytes
> GC: 10, GC time: 0.688 sec.
> NIL
> 
> 
> I don't want to document this option, because the default GC frequency
> is completely sufficient for the average user.
> 
> Bruno
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> clisp-devel mailing list
> cli...@li...
> https://lists.sourceforge.net/lists/listinfo/clisp-devel