At Sat, 22 Mar 2008 17:18:58 +0100,
Joachim Breitner wrote:
>
> Hi,
>
> Am Donnerstag, den 20.03.2008, 18:01 +0900 schrieb Junichi Uekawa:
> > > > I saw this patch on LKML,=20
> > > >=20
> > > > > This should exit 0 and show "wait status 0xb7f", and does on i386.=20
> > > > > On 2.6.24 it exits 1 and shows "wait status 0xb".=20
> > > > >=20
> > > > > Note, on the current tree before [PATCH] x86_64: fix iret exception
> > > > > rec=
> > > overy=20
> > > > > that I also posted today, this will instead produce pathological
> > > > > weirdn=
> > > ess=20
> > > > > probably with a quick crash or silent reboot, from running with the
> > > > > wro=
> > > ng GS.=20
> > > >=20
> > > > amd64 running i386 chroot on 2.6.24 kernel may jump into this problem.
> > > > Is this your case?
> > >
> > > No, this is a regular i386 single-core machine (Thinkpad T41p), sorry...
> >
> > Is it possible for you to install what is in the tip of Git tree, or
> > try running cowdancer inside the chroot with the following patch ?
>
> I applied the patch to cowdancer in unstable.
>
> Here is the relevant output (newline added manually):
>
> Preparing to replace tzdata 2007k-2 (using .../tzdata_2008a-1_all.deb) ...
> Unpacking replacement tzdata ...
> Can not write log, openpty() failed (/dev/pts not mounted?)
> Setting up tzdata (2008a-1) ...
> cowdancer: unexpected WIFEXITED status in waitpid: 8105548
> /var/lib/dpkg/info/tzdata.postinst: line 29: /etc/timezone: Cannot allocate
> memory
>
> Not sure if that helps,
Provided that output is correct, it's terminated with a signal 72.
REAL csh: printf("%i\n", WIFSTOPPED(0x8105548));
0
REAL csh: printf("%i\n", WIFCONTINUED(0x8105548));
0
REAL csh: printf("%i\n", WIFEXITED(0x8105548));
0
REAL csh: printf("%i\n", WIFSIGNALED(0x8105548));
1
REAL csh: printf("%i\n", WTERMSIG(0x8105548));
72
But I should have had another check. Humph, well, I kind of know the
root cause now this is a minor point.
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
