> You may want to try running the process under valgrind.
Thanks. I'm trying that but have been so far unable to get valgrind
to report any problems within Python or our libraries before that
message, just a couple things at startup which seem to occur before
Python gets going:
==21374== Invalid
On Tue, 2013-06-11 at 12:14 -0700, Benjamin Peterson wrote:
> 2013/6/11 Skip Montanaro :
> > I encountered this disconcerting message yesterday on a Linux system
> > running Python 2.7.2:
> >
> > *** glibc detected *** /opt/local/bin/python: corrupted double-linked
> > list: 0x03b01c90 ***
2013/6/11 Skip Montanaro :
> I encountered this disconcerting message yesterday on a Linux system
> running Python 2.7.2:
>
> *** glibc detected *** /opt/local/bin/python: corrupted double-linked
> list: 0x03b01c90 ***
I suspect that's a corrupt linked list interal to glibc.
--
Regards,
I encountered this disconcerting message yesterday on a Linux system
running Python 2.7.2:
*** glibc detected *** /opt/local/bin/python: corrupted double-linked
list: 0x03b01c90 ***
Of course, no core file or other information about where the problem
occurred was left behind, just the raw
