Daniel Burrows wrote:
On Sun, Jul 08, 2007 at 04:21:35PM +0800, manphiz <[EMAIL PROTECTED]> was heard
to say:
Here it is the backtrace of optimization-free aptitude with libc6-i686, and
I don't think it can be much helpful, as it doesn't provide more
information than the optimized one.
(Forgotten to CC to BTS, however the previous information is helpless)
Yeah, that was disappointing. I wonder what happens if you run
aptitude in valgrind? Install valgrind and run
valgrind --log-file=/tmp/aptitude.log /path/to/your/aptitude/compile
If something really is smashing the stack, it should (hah, *should*)
show up there.
Daniel
I tried valgrind with libc6-i686 installed, and it completely confused
me: when aptitude was run with valgrind, it mysteriously regained focus
after 'g'! I double checked with(without) valgrind, and it definitely
losted focus without valgrind, and worked fine with valgrind! I can't
tell why and, as it actually ran fine, I don't know if this valgrind log
can be helpful. I've also got a verbose log, which is over 20k, which I
don't think will be helpful either, but if it's needed please let me know.
==9477== Memcheck, a memory error detector.
==9477== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==9477== Using LibVEX rev 1732, a library for dynamic binary translation.
==9477== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==9477== Using valgrind-3.2.3-Debian, a dynamic binary instrumentation
framework.
==9477== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==9477== For more details, rerun with: -v
==9477==
==9477== My PID = 9477, parent PID = 6214. Prog and args are:
==9477== aptitude
==9477==
==9477==
==9477== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 37 from 2)
==9477== malloc/free: in use at exit: 8,353,081 bytes in 147,590 blocks.
==9477== malloc/free: 3,954,768 allocs, 3,807,178 frees, 140,699,107 bytes
allocated.
==9477== For counts of detected errors, rerun with: -v
==9477== searching for pointers to 147,590 not-freed blocks.
==9477== checked 16,109,412 bytes.
==9477==
==9477== LEAK SUMMARY:
==9477== definitely lost: 14,122 bytes in 655 blocks.
==9477== possibly lost: 4,280,746 bytes in 73,529 blocks.
==9477== still reachable: 4,058,213 bytes in 73,406 blocks.
==9477== suppressed: 0 bytes in 0 blocks.
==9477== Rerun with --leak-check=full to see details of leaked memory.
