new zsh build hang on sparkylinux (essentially debian test)

new zsh build hang on sparkylinux (essentially debian test)

[Vin Shelton]

[-- Attachment #1: Type: text/plain, Size: 1736 bytes --]

Hi,

I just installed the most recent version of sparky linux (it is based on
debian testing).  I built zsh and the newly-built zsh hangs.  Here is the
tail of

strace ./Src/zsh -f

socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 11
connect(11, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) =
-1 ENOENT (No such file or directory)
close(11)                               = 0
socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 11
connect(11, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) =
-1 ENOENT (No such file or directory)
close(11)                               = 0
open("/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 11
fstat(11, {st_mode=S_IFREG|0644, st_size=513, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f46a902c000
read(11, "# /etc/nsswitch.conf\n#\n# Example"..., 4096) = 513
brk(0x26dc000)                          = 0x26dc000
read(11, "", 4096)                      = 0
close(11)                               = 0
munmap(0x7f46a902c000, 4096)            = 0
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 11
fstat(11, {st_mode=S_IFREG|0644, st_size=130393, ...}) = 0
mmap(NULL, 130393, PROT_READ, MAP_PRIVATE, 11, 0) = 0x7f46a900d000
close(11)                               = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
directory)
open("/lib/x86_64-linux-gnu/libnss_compat.so.2", O_RDONLY|O_CLOEXEC) = 11
read(11,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320\22\0\0\0\0\0\0"...,
832) = 832
fstat(11, {st_mode=S_IFREG|0644, st_size=31616, ...}) = 0
^C--- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL} ---
+++ killed by SIGINT +++


Does anyone have any idea as to what may be going on?

  - Vin

Re: new zsh build hang on sparkylinux (essentially debian test)

[Bart Schaefer]

[-- Attachment #1: Type: text/plain, Size: 545 bytes --]

On May 11, 2016 6:08 PM, "Vin Shelton" <ethersoft@gmail.com> wrote:
>
> I just installed the most recent version of sparky linux (it is based on
> debian testing).  I built zsh and the newly-built zsh hangs.

> open("/lib/x86_64-linux-gnu/libnss_compat.so.2", O_RDONLY|O_CLOEXEC) = 11
> read(11,
> "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320\22\0\0\0\0\0\0"...,
> 832) = 832
> fstat(11, {st_mode=S_IFREG|0644, st_size=31616, ...}) = 0

My best guess is that's attempting to do getpwnam() but the (simulated?)
NSS query is not returning.

Re: new zsh build hang on sparkylinux (essentially debian test)

[Vin Shelton]

[-- Attachment #1: Type: text/plain, Size: 992 bytes --]

Dear Workers,

On Wed, May 11, 2016 at 9:57 PM, Bart Schaefer <schaefer@brasslantern.com>
 wrote:

> On May 11, 2016 6:08 PM, "Vin Shelton" <ethersoft@gmail.com> wrote:
> >
> > I just installed the most recent version of sparky linux (it is based on
> > debian testing).  I built zsh and the newly-built zsh hangs.
>
> > open("/lib/x86_64-linux-gnu/libnss_compat.so.2", O_RDONLY|O_CLOEXEC) = 11
> > read(11,
> > "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320\22\0\0\0\0\0\0"...,
> > 832) = 832
> > fstat(11, {st_mode=S_IFREG|0644, st_size=31616, ...}) = 0
>
> My best guess is that's attempting to do getpwnam() but the (simulated?)
> NSS query is not returning.
>

Thanks, Bart.

Just for the record, this actually ended up being something to do with the
compiler optimization settings.  Building with CFLAGS=-O yielded a working
zsh.

$ uname -a
Linux nuc 4.5.0-2-amd64 #1 SMP Debian 4.5.3-2 (2016-05-08) x86_64 GNU/Linux

$ gcc --version
gcc (Debian 5.3.1-17) 5.3.1 20160429

  - Vin

Re: new zsh build hang on sparkylinux (essentially debian test)

[Bart Schaefer]

Belated reply here, I've been traveling ... question directed at -workers,
not at Vin:

On May 13, 11:20pm, Vin Shelton wrote:
}
} Just for the record, this actually ended up being something to do with the
} compiler optimization settings.  Building with CFLAGS=-O yielded a working
} zsh.

Does our "configure" assure that the test cases are run with the same
compiler optimization flags as the final build?

Obviously compiler optimization isn't intended to change semantics, but
there may be some behavior that differs among standards and we're relying
on some variant that occurs when the build is not optimized.

Re: new zsh build hang on sparkylinux (essentially debian test)

[Daniel Shahaf]

Bart Schaefer wrote on Wed, Jun 01, 2016 at 18:05:14 -0700:
> Does our "configure" assure that the test cases are run with the same
> compiler optimization flags as the final build?

Datapoint: the zsh_cv_c_have_union_init AC_TRY_COMPILE() check happens
before adding the output of `pcre-config --cflags` to CPPFLAGS.  

Cheers,

Daniel
(Bart: thanks for 38569; it'll take me more time to digest it)

> Obviously compiler optimization isn't intended to change semantics, but
> there may be some behavior that differs among standards and we're relying
> on some variant that occurs when the build is not optimized.