tiomap-dev team mailing list archive
-
tiomap-dev team
-
Mailing list archive
-
Message #00357
[Bug 599862] Re: pth_init() aborts on armel with "longjmp causes uninitialized stack frame"
I thought there was a runtime issue as well (not just make test)?! (The
original bug mentions some abort when using gnupg.)
I understand that when getcontext() is missing, pth defaults to another
pth backend which either is broken in pth itself or exposes a bug in
eglibc; I'd like to make sure that we track this issue.
--
You received this bug notification because you are a member of TI OMAP
Developers, which is a direct subscriber.
https://bugs.launchpad.net/bugs/599862
Title:
pth_init() aborts on armel with "longjmp causes uninitialized stack frame"
Status in “gnupg2” package in Ubuntu:
Invalid
Status in “pth” package in Ubuntu:
Fix Released
Bug description:
Binary package hint: gnupg2
I cannot launch gnupg-agent on my platform:
$ gpg-agent --daemon
*** longjmp causes uninitialized stack frame ***: gpg-agent terminated
Aborted
This is on an armel maverick system.
More information:
$ lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10
$ apt-cache policy gnupg2
gnupg2:
Installed: (none)
Candidate: 2.0.14-1.1ubuntu1
Version table:
2.0.14-1.1ubuntu1 0
500 http://ports.ubuntu.com/ubuntu-ports/ maverick/main Packages