On Wed, 2010-08-25 at 02:26 +0200, Alexis ROBERT wrote: > Something more like ... this ? :) > > Program received signal SIGABRT, Aborted. > 0xb7fe1424 in __kernel_vsyscall () > (gdb) backtrace
> #6 0xb7ef21cd in free () from /lib/libc.so.6 > #7 0x080522a6 in func_sort ( > o=0xc6d9eb4 " t/host/linux-x86/bin/accRuntimeTest > out/host/linux-x86/bin/run-core-tests-on-ri > out/target/product/generic/data/app/AndroidCommonTests.apk > neric/system/bin/qemu-props\fw*x\f\202'x\f1", argv=0xbfffd5e0, > funcname=0x806b201 "sort") at function.c:1183 Wow, this is very strange. All I can assume is that there's some memory corruption here because the malloc/free in func_sort() looks correct to me. Are those special characters in that string (e.g., is "\202" a 4-char string of "\", "2", "0", "2", or is it a single character with value 0202)? Ditto for the "\f"; is that one or two characters? Do those characters appear in the actual makefile somewhere, or is this the result of some kind of corruption? If you happen to have valgrind installed it would be interesting to run the make instance inside valgrind and see what it complains about. Are you somewhat proficient with GDB? If I suggested some breakpoints to set and things to print would you be able to do that? -- ------------------------------------------------------------------------------- Paul D. Smith <psm...@gnu.org> Find some GNU make tips at: http://www.gnu.org http://make.mad-scientist.net "Please remain calm...I may be mad, but I am a professional." --Mad Scientist _______________________________________________ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
