[maemo-developers] how to get crash stack trace in Maemo 2.2 (Nokia 770)

[From: Eero Tamminen]

Hi,

ext Han wrote:
> On Tue, Aug 31, 2010 at 8:37 AM, Eero Tamminen <eero.tamminen at nokia.com> wrote:
> I tried Valgrind, and it did report memory leaks.  However, most are
> from gtk/gdk libs and not obvious to me if something is wrong in my
> program. For example:
> 
> ==19494== 2,356 (256 direct, 2,100 indirect) bytes in 1 blocks are
> definitely lost in loss record 5,620 of 5,662
> ==19494==    at 0x4024D12: realloc (vg_replace_malloc.c:476)
> ==19494==    by 0x4747951: ??? (in /usr/lib/libfontconfig.so.1.3.0)
> ==19494==    by 0x47483C7: ??? (in /usr/lib/libfontconfig.so.1.3.0)
> ==19494==    by 0x4748A0B: ??? (in /usr/lib/libfontconfig.so.1.3.0)
> ==19494==    by 0x4748A4F: ??? (in /usr/lib/libfontconfig.so.1.3.0)
> ==19494==    by 0x473CE25: FcDefaultSubstitute (in
> /usr/lib/libfontconfig.so.1.3.0)

You can probably ignore all fontconfig "leaks".  Fontconfig does stupid
pointer tricks (uses offsets instead of actual pointers) so that
Valgrind cannot know whether fontconfig still retains a pointer to
its allocations.

Note that after you've fixed some leaks, Valgrinding again may reveal
new leaks, Valgrind doesn't always see all leaks when there are lots
of them.


	- Eero