------- Comment #4 from sega01 at go-beyond dot org 2009-04-23 01:10 ------- (In reply to comment #3) > It might be better if you use gdb instead of using ltrace because those two > programs don't give enough information on what is going on. This could be > still a bug in Lua or even in glibc itself but without a testcase to figure > out > what is going wrong it is hard to debug. >
I can give gdb a try, but will let this sit for tonight first. For clarity, nothing on my system is compiled with GCC 4.4.0 except glibc 2.8 for when I test. Lua, xz, vi, nano, and all of the programs that segfault only segfault when I use the GCC 4.4.0 compiled glibc 2.8; if I use glibc 2.8 built with GCC 4.3.3 they run just fine. I don't think this is a bug in any of those programs. I think this could be a glibc bug, but I'm leaning on GCC since GCC 4.3.3 builds a clean glibc. Thanks, Teran -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39852
