* Re: Bug#247556: zsh build gets stuck running tests.
[not found] <20040505194300.GA3142@ping.be>
@ 2004-05-05 20:58 ` Clint Adams
2004-05-05 21:08 ` Kurt Roeckx
0 siblings, 1 reply; 11+ messages in thread
From: Clint Adams @ 2004-05-05 20:58 UTC (permalink / raw)
To: zsh-workers; +Cc: Kurt Roeckx, 247556-forwarded
I don't know the cause, but this has happened in the past on sparc(64),
though only under sbuild (a perl script).
On Wed, May 05, 2004 at 09:43:00PM +0200, Kurt Roeckx wrote:
>
> When building the package on amd64, it runs fine until it gets to this
> point:
> ../../Test/B03print.ztst: starting.
> ../../Test/B03print.ztst: all tests successful.
> ../../Test/B04read.ztst: starting.
>
> Then you see this in ps:
>
> root 18855 0.0 0.2 5580 1140 ? TN 19:31 0:00 sh -c dpkg-buildpackage -us -uc -B -r/usr/bin/fakeroot 2>&1
> root 18856 0.0 0.2 5616 1236 ? TN 19:31 0:00 /bin/sh /usr/bin/dpkg-buildpackage -us -uc -B -r/usr/bin/fakeroot
> root 18982 0.0 0.1 5412 848 ? TN 19:31 0:00 /usr/bin/make -f
> debian/rules build
> root 31972 0.0 0.2 5572 1144 ? TN 19:35 0:00 /bin/sh -c cd obj && /usr/bin/make check
> root 31973 0.0 0.2 5692 1104 ? TN 19:35 0:00 /usr/bin/make check
> root 31974 0.0 0.2 5572 1144 ? TN 19:35 0:00 /bin/sh -c cd Test ; /usr/bin/make check
> root 31975 0.0 0.1 5412 840 ? TN 19:35 0:00 /usr/bin/make check
> root 32150 0.0 0.2 5584 1168 ? TN 19:35 0:00 /bin/sh -c for f in ../../Test/*.ztst; do ../Src/zsh +Z -f ../../Test/ztst.zsh
> $f; done root 728 0.0 0.3 13704 1680 ? TN 19:35 0:00 ../Src/zsh +Z -f ../../Test/ztst.zsh ../../Test/B04read.ztst
>
> As you can see all the processes are suddenly stuck in state "T",
> straced/stopped.
>
> I can get them all back to working using KILL -CONT, but if I do
> the same on the last process (pid 728, the test), they all end up
> in stop again.
>
> I then tried to strace it, and get then get this all over and
> over again:
> --- SIGTTOU (Stopped (tty output)) @ 0 (0) ---
> --- SIGTTOU (Stopped (tty output)) @ 0 (0) ---
> ioctl(11, SNDCTL_TMR_STOP or TCSETSW, {B38400 opost isig -icanon
> echo ...}) = ?
> ERESTARTSYS (To be restarted)
>
> If I kill -9 728 and -CONT the rest the build goes on fine and
> says it's succesful.
>
> Anybody got any idea what might be wrong or how I can test what's
> really going on?
>
>
> Kurt
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Bug#247556: zsh build gets stuck running tests.
2004-05-05 20:58 ` Bug#247556: zsh build gets stuck running tests Clint Adams
@ 2004-05-05 21:08 ` Kurt Roeckx
2004-05-05 21:24 ` Clint Adams
0 siblings, 1 reply; 11+ messages in thread
From: Kurt Roeckx @ 2004-05-05 21:08 UTC (permalink / raw)
To: Clint Adams; +Cc: zsh-workers, 247556-forwarded
On Wed, May 05, 2004 at 04:58:40PM -0400, Clint Adams wrote:
> I don't know the cause, but this has happened in the past on sparc(64),
> though only under sbuild (a perl script).
This is under sbuild too.
Kurt
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Bug#247556: zsh build gets stuck running tests.
2004-05-05 21:08 ` Kurt Roeckx
@ 2004-05-05 21:24 ` Clint Adams
2004-05-05 21:35 ` Kurt Roeckx
0 siblings, 1 reply; 11+ messages in thread
From: Clint Adams @ 2004-05-05 21:24 UTC (permalink / raw)
To: Kurt Roeckx; +Cc: zsh-workers, 247556, sbuild, elmo
> > I don't know the cause, but this has happened in the past on sparc(64),
> > though only under sbuild (a perl script).
>
> This is under sbuild too.
sbuild appears to deal with the following signals at various points of
execution: HUP INT TERM ALRM PIPE QUIT
Are you building 32- or 64-bit?
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Bug#247556: zsh build gets stuck running tests.
2004-05-05 21:24 ` Clint Adams
@ 2004-05-05 21:35 ` Kurt Roeckx
2004-05-05 22:06 ` Clint Adams
0 siblings, 1 reply; 11+ messages in thread
From: Kurt Roeckx @ 2004-05-05 21:35 UTC (permalink / raw)
To: Clint Adams; +Cc: zsh-workers, 247556, sbuild, elmo
On Wed, May 05, 2004 at 05:24:23PM -0400, Clint Adams wrote:
> > > I don't know the cause, but this has happened in the past on sparc(64),
> > > though only under sbuild (a perl script).
> >
> > This is under sbuild too.
>
> sbuild appears to deal with the following signals at various points of
> execution: HUP INT TERM ALRM PIPE QUIT
>
> Are you building 32- or 64-bit?
It's all 64bit here.
Kurt
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Bug#247556: zsh build gets stuck running tests.
2004-05-05 21:35 ` Kurt Roeckx
@ 2004-05-05 22:06 ` Clint Adams
2004-05-05 22:23 ` Kurt Roeckx
0 siblings, 1 reply; 11+ messages in thread
From: Clint Adams @ 2004-05-05 22:06 UTC (permalink / raw)
To: Kurt Roeckx; +Cc: zsh-workers, 247556, sbuild, troup
> > > > I don't know the cause, but this has happened in the past on sparc(64),
> > > > though only under sbuild (a perl script).
> > >
> > > This is under sbuild too.
> >
> > sbuild appears to deal with the following signals at various points of
> > execution: HUP INT TERM ALRM PIPE QUIT
> >
> > Are you building 32- or 64-bit?
>
> It's all 64bit here.
So we have a problem which only seems to occur when building zsh under
sbuild on sparc and amd64. Kernel bug?
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Bug#247556: zsh build gets stuck running tests.
2004-05-05 22:06 ` Clint Adams
@ 2004-05-05 22:23 ` Kurt Roeckx
2004-05-05 22:32 ` Clint Adams
0 siblings, 1 reply; 11+ messages in thread
From: Kurt Roeckx @ 2004-05-05 22:23 UTC (permalink / raw)
To: Clint Adams; +Cc: zsh-workers, 247556, sbuild, troup
On Wed, May 05, 2004 at 06:06:57PM -0400, Clint Adams wrote:
>
> So we have a problem which only seems to occur when building zsh under
> sbuild on sparc and amd64. Kernel bug?
Why would it be a kernel bug if all other packages build fine?
Btw, I was just taking a closer look at other zsh bug reports and
maybe #168215 is related?
Anyway, 4.2.0-dev-1+20040504-1 didn't have the problem at all.
Kurt
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Bug#247556: zsh build gets stuck running tests.
2004-05-05 22:23 ` Kurt Roeckx
@ 2004-05-05 22:32 ` Clint Adams
2004-05-05 23:33 ` Kurt Roeckx
0 siblings, 1 reply; 11+ messages in thread
From: Clint Adams @ 2004-05-05 22:32 UTC (permalink / raw)
To: Kurt Roeckx; +Cc: zsh-workers, 247556, sbuild, troup
> Why would it be a kernel bug if all other packages build fine?
Why would it be a zsh bug if it builds fine outside of sbuild?
Why would it be an sbuild bug if it builds fine under sbuild on all
architectures bug sparc and amd64?
> Btw, I was just taking a closer look at other zsh bug reports and
> maybe #168215 is related?
Perhaps. That situation also involves zsh, perl, and weird signal
problems.
> Anyway, 4.2.0-dev-1+20040504-1 didn't have the problem at all.
The zsh-beta package doesn't run "make check", so the problem wouldn't
be observed.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Bug#247556: zsh build gets stuck running tests.
2004-05-05 22:32 ` Clint Adams
@ 2004-05-05 23:33 ` Kurt Roeckx
2004-05-06 11:24 ` Peter Stephenson
2004-05-07 1:32 ` Clint Adams
0 siblings, 2 replies; 11+ messages in thread
From: Kurt Roeckx @ 2004-05-05 23:33 UTC (permalink / raw)
To: Clint Adams; +Cc: zsh-workers, 247556, sbuild, troup
On Wed, May 05, 2004 at 06:32:37PM -0400, Clint Adams wrote:
> > Why would it be a kernel bug if all other packages build fine?
>
> Why would it be a zsh bug if it builds fine outside of sbuild?
> Why would it be an sbuild bug if it builds fine under sbuild on all
> architectures bug sparc and amd64?
Anyway, I'm using kernel version 2.6.5. I doubt many other
people using sbuild on 2.6.x.
What is the test that triggers it (B04read.ztst) doing that other
tests aren't doing? It would be nice if reduce it to something
we can easily reproduce.
I ran:
strace -f -F zsh +Z -f Test/B04read.ztst
and got:
[...]
open("/bin", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = 3
fstat(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
fcntl(3, F_SETFD, FD_CLOEXEC) = 0
getdents64(3, /* 96 entries */, 4096) = 2736
getdents64(3, /* 0 entries */, 4096) = 0
close(3) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [CHLD], 8) = 0
pipe([3, 4]) = 0
fork(Process 24898 attached
) = 24898
[pid 24894] close(4 <unfinished ...>
[pid 24898] close(3 <unfinished ...>
[pid 24894] <... close resumed> ) = 0
[pid 24894] read(3, <unfinished ...>
[pid 24898] <... close resumed> ) = 0
[pid 24898] close(11) = 0
[pid 24898] rt_sigaction(SIGQUIT, {SIG_DFL}, {SIG_IGN}, 8) = 0
[pid 24898] times({tms_utime=0, tms_stime=0, tms_cutime=0,
tms_cstime=0}) = 551580957
[pid 24898] close(4) = 0
[pid 24894] <... read resumed> "", 1) = 0
[pid 24894] close(3) = 0
[pid 24894] rt_sigprocmask(SIG_BLOCK, [CHLD], [CHLD], 8) = 0
[pid 24894] rt_sigsuspend(~[HUP CHLD] <unfinished ...>
[pid 24898] open("world", O_WRONLY|O_CREAT|O_TRUNC|O_NOCTTY,
0666) = 3
[pid 24898] dup2(3, 1) = 1
[pid 24898] close(3) = 0
[pid 24898] close(10) = 0
[pid 24898] close(4294967295) = -1 EBADF (Bad file
descriptor)
[pid 24898] close(4294967295) = -1 EBADF (Bad file
descriptor)
[pid 24898] rt_sigprocmask(SIG_UNBLOCK, [CHLD], [CHLD], 8) = 0
[pid 24898] execve("/bin/cat", ["cat"], [/* 13 vars */]) = 0
[pid 24898] uname({sys="Linux", node="debian", ...}) = 0
[pid 24898] brk(0) = 0x505000
[pid 24898] mmap(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2a95569000
[pid 24898] access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No
such file or directory)
[pid 24898] open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No
such file or directory)
[pid 24898] open("/etc/ld.so.cache", O_RDONLY) = 3
[pid 24898] fstat(3, {st_mode=S_IFREG|0644, st_size=52453, ...})
= 0
[pid 24898] mmap(NULL, 52453, PROT_READ, MAP_PRIVATE, 3, 0) =
0x2a9556a000
[pid 24898] close(3) = 0
[pid 24898] access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No
such file or directory)
[pid 24898] open("/lib/libc.so.6", O_RDONLY) = 3
[pid 24898] read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\240\331"..., 640)
= 640
[pid 24898] fstat(3, {st_mode=S_IFREG|0644, st_size=1268960,
...}) = 0
[pid 24898] mmap(NULL, 2329544, PROT_READ|PROT_EXEC, MAP_PRIVATE,
3, 0) = 0x2a9566b000
[pid 24898] mprotect(0x2a95785000, 1174472, PROT_NONE) = 0
[pid 24898] mmap(0x2a9586b000, 217088, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED, 3, 0x100000) = 0x2a9586b000
[pid 24898] mmap(0x2a958a0000, 15304, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x2a958a0000
[pid 24898] close(3) = 0
[pid 24898] mmap(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2a958a4000
[pid 24898] munmap(0x2a9556a000, 52453) = 0
[pid 24898] brk(0) = 0x505000
[pid 24898] brk(0x526000) = 0x526000
[pid 24898] brk(0) = 0x526000
[pid 24898] fstat(1, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
[pid 24898] fstat(0, {st_mode=S_IFCHR|0600, st_rdev=makedev(136,
1), ...}) = 0
[pid 24898] read(0, <unfinished ...>
And there it hangs reading from stdin and nobody seems to be
writing.
Kurt
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Bug#247556: zsh build gets stuck running tests.
2004-05-05 23:33 ` Kurt Roeckx
@ 2004-05-06 11:24 ` Peter Stephenson
2004-05-07 1:32 ` Clint Adams
1 sibling, 0 replies; 11+ messages in thread
From: Peter Stephenson @ 2004-05-06 11:24 UTC (permalink / raw)
To: Kurt Roeckx; +Cc: zsh-workers, 247556
Kurt Roeckx wrote:
> What is the test that triggers it (B04read.ztst) doing that other
> tests aren't doing? It would be nice if reduce it to something
> we can easily reproduce.
Simply reducing the tests in B04read.ztst should do this. There's no
interdependence in that file. My favourite would be this one:
read -k3 -u0 <<<foo:bar
print $REPLY
0:read specified number of chars
>foo
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK Tel: +44 (0)1223 692070
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Bug#247556: zsh build gets stuck running tests.
2004-05-05 23:33 ` Kurt Roeckx
2004-05-06 11:24 ` Peter Stephenson
@ 2004-05-07 1:32 ` Clint Adams
2004-05-08 16:02 ` Kurt Roeckx
1 sibling, 1 reply; 11+ messages in thread
From: Clint Adams @ 2004-05-07 1:32 UTC (permalink / raw)
To: Kurt Roeckx; +Cc: zsh-workers, 247556, sbuild, troup
> And there it hangs reading from stdin and nobody seems to be
> writing.
zsh-beta 4.2.0-dev-1+20040505-1 runs "make check". Does it exhibit the
same problem?
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Bug#247556: zsh build gets stuck running tests.
2004-05-07 1:32 ` Clint Adams
@ 2004-05-08 16:02 ` Kurt Roeckx
0 siblings, 0 replies; 11+ messages in thread
From: Kurt Roeckx @ 2004-05-08 16:02 UTC (permalink / raw)
To: Clint Adams; +Cc: zsh-workers, 247556, sbuild, troup
On Thu, May 06, 2004 at 09:32:11PM -0400, Clint Adams wrote:
>
> zsh-beta 4.2.0-dev-1+20040505-1 runs "make check". Does it exhibit the
> same problem?
Yes. Under sbuild it gets stuck. Under dpkg-buildpackage there
is no problem.
Kurt
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2004-05-08 16:02 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20040505194300.GA3142@ping.be>
2004-05-05 20:58 ` Bug#247556: zsh build gets stuck running tests Clint Adams
2004-05-05 21:08 ` Kurt Roeckx
2004-05-05 21:24 ` Clint Adams
2004-05-05 21:35 ` Kurt Roeckx
2004-05-05 22:06 ` Clint Adams
2004-05-05 22:23 ` Kurt Roeckx
2004-05-05 22:32 ` Clint Adams
2004-05-05 23:33 ` Kurt Roeckx
2004-05-06 11:24 ` Peter Stephenson
2004-05-07 1:32 ` Clint Adams
2004-05-08 16:02 ` Kurt Roeckx
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).