This constant selection in glibc seems quite deliberate, according to
Alan's commit message upstream:
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=f7c399cff5bd04ee9dc117fb6b0f39597dc047c6
This leads one to wonder if perhaps the kernel is wrong here, or if
ltp's just being silly. I'm no
Ok I have tried this out on postal02, configured LTP as below:
./configure --build powerpc64le-linux-gnu --target powerpc64le-
linux-gnu
The test fails as indicated. I have fiddled with the parameters and
using 2048-1 as the limit triggers the test correctly, though
MINSIGSTKSZ is 4096. The
The Ubuntu-3.13.0-0.15 kernel has been copied into the bootstrap archive
and should be available for update. This kernel is based on the
v3.13-rc7 kernel. If we could retest with that kernel that would help.
Please report any testing here.
** Changed in: linux (Ubuntu)
Assignee: (unassigned)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267062
Title:
sigaltstack system call unable to sen
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267062
Title:
sigaltstack system call unable to send proper return code (error12)
