← Back to team overview

tiomap-dev team mailing list archive

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

 

This bug was fixed in the package pth - 2.0.7-16ubuntu2

---------------
pth (2.0.7-16ubuntu2) natty; urgency=low

  * debian/rules: disable FORTIFY_SOURCE for armel build, as it breaks
    the sigjmp/longjmp mechanism used on ARM for user space threading.
    (Closes LP: #599862)
 -- Jani Monoses <jani@xxxxxxxxxx>   Mon, 03 Jan 2011 15:04:54 +0200

** Changed in: pth (Ubuntu)
       Status: Triaged => Fix Released

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