Re: [ast-users] [ast-developers] New AST Toolkit and ksh93 beta release posted.
On Thu, Oct 09, 2014 at 08:53:20PM -0400, David Korn wrote:
I tried to preallocate a number of siginfo_t's but it is possible to still
require malloc().
One way of avoiding this is to use a /tmp fiile. With sftmp() you can
specify a size that will allow it to use memory and only create a file if
it overflows.
Use of malloc() in a signal handler must be avoided at all costs. It
is illegal under POSIX since it is not an async-signal-safe function
(see at the end of section 2.4.3 for a list of the legal functions that
can be called while in signal handling context
http://pubs.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.html)
Using malloc() in a signal handler, even rarely, will still lead to random
deadlocks on many systems.
Quentin
On Thu, Oct 9, 2014 at 9:24 AM, Dr. Werner Fink [1]wer...@suse.de wrote:
On Tue, Oct 07, 2014 at 09:27:17PM -0400, David Korn wrote:
A new beta version of the AST Toolkit and ksh93 have posted on the
ATT
website, [2]http://www.research.att.com/sw/download. Click on the
word beta
on the left side of this download page.
There are many significant new features for ksh93 in the last six
months as
well as many bug fixes. Here are some of the new features. The
RELEASE
file
in the ksh93 source directory has a log of all the changes. Here are
some
of the highlights.
1. Bash style programmable command completion.
2. A bash compatibility mode which runs many more bash scripts
without
change. When in this mode, the shell uses dynamic scoping for
functions
and function name, and name() are equivalent.
3. The read command can read json format files to create a ksh93
compound
variable with the read -m json. It is already able to write ksh93
compound variables in json format.
4. The jobs command how displays the directory in which the command
was
started if it is not the current directory. This is a bash
feature that
I found useful.
5. The expansion ${$variable} to get the value of the variable named
by
variable.
6. Several options have been added to commands to aide in Bash
compatibility.
This version still uses malloc() within signal handler which is evil.
I see still random hanging build processes and all of them show the
same problem: malloc() within a signal handler[1]. Beside this: it
is not possible to use the glibc malloc().
IMHO there have to an other way to get the siginfo_t informations from
the
signal handler down to the normal ksh process flow.
Werner
[1] [3]http://linux.die.net/man/3/sigaction
--
Having a smoking section in a restaurant is like having
a peeing section in a swimming pool. -- Edward Burr
___
ast-developers mailing list
[4]ast-develop...@lists.research.att.com
[5]http://lists.research.att.com/mailman/listinfo/ast-developers
References
Visible links
1. mailto:wer...@suse.de
2. http://www.research.att.com/sw/download
3. http://linux.die.net/man/3/sigaction
4. mailto:ast-develop...@lists.research.att.com
5. http://lists.research.att.com/mailman/listinfo/ast-developers
___
ast-users mailing list
ast-users@lists.research.att.com
http://lists.research.att.com/mailman/listinfo/ast-users
Quentin
___
ast-users mailing list
ast-users@lists.research.att.com
http://lists.research.att.com/mailman/listinfo/ast-users
Re: [ast-users] ast-ksh failing to build on RHEL7
The 20140929 release now builds successfully under RHEL7.
On Wed, Aug 27, 2014 at 5:10 PM, Quentin Barnes qbar...@gmail.com wrote:
Any update on this problem yet?
On Sun, Aug 3, 2014 at 4:50 PM, Quentin Barnes qbar...@gmail.com wrote:
Welcome back! I hope you had a good vacation.
The iffe.out file contents can be found here: https://pastee.org/fdpex
The iffe-{sh,ksh,bash}.out files all were identical in size and contents.
What else can I try for you?
On Sat, Jul 26, 2014 at 10:37 AM, Glenn Fowler glenn.s.fow...@gmail.com
wrote:
sorry for the delay
still recovering from vacation
run this:
---
cd /home/qbarnes/ksh-20140625/arch/linux.i386-64/src/lib/libast
iffe -d2 -v -X ast -X std -c 'cc -D_BLD_DLL -fPIC -D_BLD_ast -O2' - run
/home/qbarnes/ksh-20140625/src/lib/libast/features/socket iffe.out 21
---
and send me iffe.out
just in case its a shell problem you can try different shells:
for sh in /bin/sh ksh etc.
do SHELL=$sh $sh iffe -v -X ast -X std -c 'cc -D_BLD_DLL -fPIC -D_BLD_ast
-O2' - run /home/qbarnes/ksh-20140625/src/lib/libast/features/socket
iffe-${sh##*/}.out
done
and compare iffe-*.out
On Sun, Jul 6, 2014 at 7:46 PM, Quentin Barnes qbar...@gmail.com wrote:
I downloaded the new beta INIT.2014-06-25 and ast-ksh.2014-06-25.
The build went fine on the RHEL6 Linux Distro (gcc 4.4.7) but went
off the rails using RHEL7 (gcc 4.8.2) failing to build the ast
library due to compilation failures.
If you compare the build logs, the first substantial difference
shows up around line 1323 with the iffe messing up sys/socket and
later with dirent. Both header problems lead directly to compile
errors later.
You can check out the logs posted here:
RHEL6 build (good): https://pastee.org/p679h
RHEL7 build (bad): https://pastee.org/5y5nk
If I compare the arch/linux.i386-64/srclib/libast/ast_socket.h
files, the RHEL7 one is missing everything including and after the
/* the socket part of ast_intercept.h */ comment line.
Any further information I can provide or ideas to try?
Quentin
___
ast-users mailing list
ast-users@lists.research.att.com
http://lists.research.att.com/mailman/listinfo/ast-users
___
ast-users mailing list
ast-users@lists.research.att.com
http://lists.research.att.com/mailman/listinfo/ast-users
