>From Dan Williams (RH) blog, there is a new debugging in glibc for memory errors. Just a warning for those unsuspecting people. remember valgrind is your friend.
---- quote --- Ok, so I guess I'm not sight-seeing today. Turns out that the reason the OOo 1.1.2-5 builds were failing was a change to glibc (a good one, just bad timing for me) that will abort() programs if they have double-frees in them. Well, guess what, OOo builds tools that evidentally have double-frees, but unfortunately the tool in question is rsc, which is a pile of crap that's 10 years old and nasty code. So maybe I can get that fixed today using the fairly quick, free wireless at OOoCon. -- Thanks KenF OpenOffice.org developer -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
