← Back to team overview

tiomap-dev team mailing list archive

[Bug 599862] Re: pth_init() aborts on armel with "longjmp causes uninitialized stack frame"

 

It happens on ARM only because it does not have the getcontext() API so
a different implementation is used for user context switching.

On non-ARM one can select the setjmp based implementation (all 3 args must be given or it will be a mix of setjmp/ucontext and it won't build) by via configure
ex:
./configure --with-mctx-mth=sjlj --with-mctx-dsp=sjlj --with-mctx-stk=ss

then make test exhibits the same error

Probably this codepath was not much tested after changes to jmpbuf in
glibc.

-- 
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:
  Triaged

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