Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Memory errors with Fedora 9 x86_64
- X-seq: zsh-workers 25070
- From: Phil Pennock <zsh-workers+phil.pennock@xxxxxxxxxxxx>
- To: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
- Subject: Re: Memory errors with Fedora 9 x86_64
- Date: Mon, 19 May 2008 00:41:29 -0700
- Cc: Zsh hackers list <zsh-workers@xxxxxxxxxx>
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=d200803; d=spodhuis.org; h=Received:Date:From:To:Cc:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To; b=YDQJsMdfY82WSqpcs8crEUVxkcexGAJ7o/WJj1dLulpQcfFgrjak9GePKisOqwWcOGt2Ki/NygMyXgNnttVLl/0Dz2NwEc/p8u+8il1V8DWg9mr7sKlPRVF6AuQdps7Qu9QcoUiFFs79GCc1v2kIhOPR+OTWEB+KCRRaz/xoXNs=;
- In-reply-to: <21272.1211041618@pws-pc>
- Mail-followup-to: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>, Zsh hackers list <zsh-workers@xxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <21272.1211041618@pws-pc>
On 2008-05-17 at 17:26 +0100, Peter Stephenson wrote:
> Having just upgraded to Fedora 9 x86_64 with kernel 2.6.25.3-18.fc9.x86_64
> and gcc 4.3.0, I'm getting occasional memory errors when running the
> tests with --enable-zsh-mem (which may or may not cause the test to
> fail, and are apparently random). I added the following debugging and the
> memory requested doesn't seem out of the ordinary. Is anyone else
> seeing anything similar?
Not here, although I am 64-bit. I'm using FreeBSD 6.2/amd64 and do not
see this; the (IMO) relevant options I set for build are:
--enable-zsh-mem --enable-zsh-secure-free
--enable-zsh-debug --enable-zsh-mem-debug
--enable-multibyte
and gcc is 3.4.6. If I build with gcc 4.2.4 then the results are
identical. Tests run eight times (5x gcc3, 3x gcc4) -- are the errors
more occasional than this?
I get one solidly repeatable test failure, working from a fresh CVS
checkout; including it below instead of starting a new thread, in case
it's a sign that I'm not running the tests correctly (I've *cough* never
run them before). I also, on one iteration of the tests against zsh
built with gcc4 got the second error below; I haven't dug into it, but
it's sleep-based, is it known to be load-sensitive? Hrm, at the same
time as that failed, the tests against zsh built with gcc3 running in
another pty hung in Y01completion.ztst. I ended up sending INT and
re-running, the tests ran to completion with only the by-now-expected
error shown.
Some blockdevice and /dev/fd/0 tests were skipped.
-Phil
Every test run (except the one which hung during this test file):
----------------------------8< cut here >8------------------------------
./Y01completion.ztst: starting.
*** /tmp/zsh.ztst.out.89827 Mon May 19 00:22:41 2008
--- /tmp/zsh.ztst.tout.89827 Mon May 19 00:22:41 2008
***************
*** 1,12 ****
line: {: }{}
DESCRIPTION:{file}
DI:{dir1}
DI:{dir2}
FI:{file1}
FI:{file2}
line: {: dir1/}{}
line: {: dir2/}{}
line: {: file1}{}
line: {: file2}{}
! line: {: dir1/}{}
! line: {: dir2/}{}
--- 1,13 ----
line: {: }{}
DESCRIPTION:{file}
+ FI:{compinit.dump}
DI:{dir1}
DI:{dir2}
FI:{file1}
FI:{file2}
+ line: {: compinit.dump}{}
line: {: dir1/}{}
line: {: dir2/}{}
line: {: file1}{}
line: {: file2}{}
! line: {: compinit.dump}{}
Test ./Y01completion.ztst failed: output differs from expected as shown above for:
comptest $': \t\t\t\t\t\t\t'
Was testing: directories and files
----------------------------8< cut here >8------------------------------
Once:
----------------------------8< cut here >8------------------------------
./C03traps.ztst: starting.
This test takes at least three seconds...
*** /tmp/zsh.ztst.out.26737 Mon May 19 00:33:52 2008
--- /tmp/zsh.ztst.tout.26737 Mon May 19 00:33:52 2008
***************
*** 1 ****
- TERM2
--- 0 ----
Test ./C03traps.ztst failed: output differs from expected as shown above for:
print -u $ZTST_fd 'This test takes at least three seconds...'
fn1() {
trap 'print TERM1' TERM
fn2() { trap 'print TERM2; return 1' TERM; sleep 2; }
fn2 &
sleep 1
kill -TERM $!
sleep 2
}
fn1
Was testing: Nested `trap ... TERM', triggered on inner loop
./C03traps.ztst: test failed.
----------------------------8< cut here >8------------------------------
Messages sorted by:
Reverse Date,
Date,
Thread,
Author