[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: python dumps core
On Tue, Apr 29, 2008 at 03:37:02AM +0200, Martin S. Weber wrote:
> On Mon, Apr 28, 2008 at 09:29:44AM +0200, Thomas Klausner wrote:
> > After updating my userland from 20080427 to 20080428 from a few hours
> > ago, many programs just segfault.
> > Example:
> > # python2.4
> > Segmentation fault (core dumped)
> > # gdb python2.4 python2.4.core
> > ...
> > (gdb) bt
> > #0 0x00007f7ffd907819 in pthread_curcpu_np () from /usr/lib/libpthread.so.0
> This ain't a critizism of ad@ .
> Since he started working, rebuilding and reinstalling a new
> userland also means coredumps in pkgsrc until the rolling-replace
> is finished. I.e. ABI -- who?
> When I've updated from .58 to .60 I've had to rebuild my perl,
> too, as pkg_chk made it dump core in each of my installed pkg's
> pkgsrc-directory. Who cares, I'm -current ...
> I'm just surprised that you're surprised about it.
This case is worse -- programs linking against libpthread don't work,
even if compiled after the upgrade directly against the new userland
without any old components. See Wolfgang's mail for details, or the
simple perl testcase from the configure script (previously in this
Main Index |
Thread Index |