Re: libc-2.10.1 causes previously well-behaved program to abort
Date: Thu, 17 Sep 2009 02:31:41 +0200 On Thu, 17 Sep 2009 02:31:41 Fredrik Rinnestam wrote:
Sorry, no. I've run 2.10.1 for a couple of months now without issues. i've even built a few iso's without trouble. are you guys sure the toolchain is ok and that there are no broken library deps? are there any specific apps (gtk, qt or whatever) that segfaults?
--
/Fredrik Rinnestam
In my case, it isn't a segfault, it's an abort. The automatic traceback that comes with it suggests that the problem lies in the interface between glib2 and libc: g_malloc calls malloc and then it aborts with a "memory corruption" error.
------------------------------
On Thu, 17 Sep 2009 10:44:33 +1000 Lucas Hazel wrote:
Neither have I. How did you upgrade?
I upgraded from the 2.6 ISO and just said yes to everything on the list, as suggested by the handbook. Then I did rejmerge, ports-u and prt-get sysup. Should I perhaps have rebuilt gtk2 against the new libc?
-- Hazel Russman <hazel_russman@yahoo.co.uk>
participants (1)
-
Hazel Russman