It looks like this is definitely a bug in pth (or something pth uses).
When libpth20 2.0.7-16 was built, it bombed out with the same error
while running tests, but the build rules silently ignore the failure :(
http://launchpadlibrarian.net/48374229/buildlog_ubuntu-maverick-
armel.pth_2.0.7-16_FU
>From the log:
=== TESTING BASIC OPERATION ===
Initializing Pth system (spawns scheduler and main thread)
*** longjmp causes uninitialized stack frame ***:
/build/buildd/pth-2.0.7/.libs/lt-test_std terminated
Aborted
[...]
make[1]: [test-std] Error 1 (ignored)
** Summary changed:
- gnupg-ag
After some fighting against some effective efforts by gdb to prevent
debugging this issue, I think I've narrowed this problem down to
something pad in pth_init() in libpth.
To demonstrate this, try applying the attached diff in gnupg2 and
rebuilding.
** Patch added: "debug.diff"
https://bugs
** Tags added: armel maverick
--
gnupg-agent won't start
https://bugs.launchpad.net/bugs/599862
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/li
