Petr Salinger ha scritto:
> Why do you think getcontext/setcontext is not available on GNU/kFreeBSD ?
> It is available for a very long time already, see i.e.
>
> http://svn.debian.org/wsvn/glibc-bsd/trunk/glibc-ports/kfreebsd/i386/getcontext.S
Oh, I probably overlooked that, so it's just armel w
wvstreams and wvdial because they rely on getcontext and
setcontext, not available in armel and kfreebsd* implementations of
eglibc (and this feature won't probably be implemented soon).
Why do you think getcontext/setcontext is not available on GNU/kFreeBSD ?
It is available for a very long tim
Luca Falavigna wrote:
> Hello Release Team,
>
> I'd like to have some guidance on how to manage bug #521473, which
> affects wvstreams and wvdial because they rely on getcontext and
> setcontext, not available in armel and kfreebsd* implementations of
> eglibc (and this feature won't probably be i
Hello Release Team,
I'd like to have some guidance on how to manage bug #521473, which
affects wvstreams and wvdial because they rely on getcontext and
setcontext, not available in armel and kfreebsd* implementations of
eglibc (and this feature won't probably be implemented soon).
I was thinking
I can confirm this on arm as well.
The wvdial error:
--> Modem initialized.
wvdial: utils/wvtask.cc:198: WvTaskMan::WvTaskMan(): Assertion
`getcontext(&get_stack_return) == 0' failed.
Aborted
wvdial --version:
WvDial 1.60
uname -a:
Linux LKGA06B66 2.6.26-1-ixp4xx #1 Sat Mar 14 08:31:13 UTC 2009
Note that this won't longer be a problem on mipsel soon
(see #523939). It still applies to other arches though.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow
6 matches
Mail list logo
