Date: Wed, 29 Dec 2010 09:44:07 +0900 (JST) From: Maho NAKATA <chat95@mac.com> To: mezz@FreeBSD.org Cc: gnome@FreeBSD.org Subject: Re: ports/153506: ports/net-im/papyon (py26-papyon-0.5.4) gets Signal 11 Message-ID: <20101229.094407.1568838937885805380.chat95@mac.com> In-Reply-To: <201012282249.oBSMnGbi007675@freefall.freebsd.org> References: <201012282249.oBSMnGbi007675@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Mezz and gnome team,
I'll close this issue since I could build on tinderbox.
> The pointyhat, tinderboxes and many users can't reproduce it. Can you run your
> Python without get crash? Here's exactly where it got crashed:
I see. It fails like follows.
gdb /usr/local/bin/python2.6
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)...
(gdb) run setup.py config
Starting program: /usr/local/bin/python2.6 setup.py config
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100334]
(no debugging symbols found)...(no debugging symbols found)...[New Thread 800e041c0 (LWP 100334)]
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 800e041c0 (LWP 100334)]
0x0000000803943550 in EVP_PKEY_CTX_dup () from /usr/local/lib/libcrypto.so.7
(gdb) bt
#0 0x0000000803943550 in EVP_PKEY_CTX_dup ()
from /usr/local/lib/libcrypto.so.7
#1 0x00000008039380af in EVP_MD_CTX_copy_ex ()
from /usr/local/lib/libcrypto.so.7
#2 0x0000000805013abe in EVPnew ()
from /usr/local/lib/python2.6/lib-dynload/_hashlib.so
#3 0x0000000805013e06 in EVP_new_md5 ()
from /usr/local/lib/python2.6/lib-dynload/_hashlib.so
#4 0x000000000047d2ed in PyEval_EvalFrameEx ()
From: mezz@FreeBSD.org
Subject: Re: ports/153506: ports/net-im/papyon (py26-papyon-0.5.4) gets Signal 11
Date: Tue, 28 Dec 2010 22:49:16 +0000 (GMT)
> Synopsis: ports/net-im/papyon (py26-papyon-0.5.4) gets Signal 11
>
> State-Changed-From-To: open->feedback
> State-Changed-By: mezz
> State-Changed-When: Tue Dec 28 22:44:42 UTC 2010
> State-Changed-Why:
> The pointyhat, tinderboxes and many users can't reproduce it. Can you run your
> Python without get crash? Here's exactly where it got crashed:
>
> bsd.python.mk:
> ------------------
> do-configure:
> @(cd ${BUILD_WRKSRC}; ${SETENV} ${MAKE_ENV} ${PYTHON_CMD} ${PYSETUP} ${PYDISTUTILS_CONFIGURE_TARGET} ${PYDISTUTILS_CONFIGUREARGS})
> ------------------
>
> Can you do it by manual to see if you can get a better error output? Or just
> remove that '@' and see if you can get more info. Try to get the backtraces
> of that crash.
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=153506
thanks,
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101229.094407.1568838937885805380.chat95>