[ARM] sysv-style ucontext functions appear not to be implemented on armel
Bug #383975 reported by
Dave Martin
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Debian |
Fix Released
|
Unknown
|
|||
glibc (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
wvstreams (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
When called, getcontext() returns -1 and sets errno = ENOSYS.
Some packages, such as wvstreams (a wvdial backend package), currently rely on the ucontext functions in order to work correctly; currently such packages are broken on armel.
See also http://
tags: | added: armel |
summary: |
- sysv-style ucontext functions appear not to be implemented on armel + [ARM] sysv-style ucontext functions appear not to be implemented on + armel |
Changed in debian: | |
status: | Unknown → New |
Changed in debian: | |
status: | New → Fix Released |
Changed in glibc (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in wvstreams (Ubuntu): | |
status: | Triaged → Fix Released |
To post a comment you must log in.
Combined this with bug #383978
----
To work around this, wvstreams should be ported to use another mechanism such as setjmp/longjmp (I haven't investigated the feasibility of this), or the affected functions (primarily setcontext and getcontext) need to be implemented in glibc.
The affected code is in utils/wvtask.cc. I don't think the functions are used anywhere else.
----
It seems that probably either ucontext should be implemented or a workaround described above for wvstreams, but it makes sense to track them both here since probably only one should be implemented and shouldn't be done blindly to the other.