http://bugzilla.novell.com/show_bug.cgi?id=559061 http://bugzilla.novell.com/show_bug.cgi?id=559061#c0 Summary: glib compiled with -fomit-frame-pointer; valgrind not patched to match Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i586 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: pth@novell.com ReportedBy: mwelinder@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091103 SUSE/3.5.5-1.1.2 Firefox/3.5.5 glib appears to be compiled with -fomit-frame-pointer: Dump of assembler code for function IA__g_malloc0: 0xb71b6930 : push %esi 0xb71b6931 : push %ebx 0xb71b6932 : call 0xb7186167 <__i686.get_pc_thunk.bx> 0xb71b6937 : add $0x836bd,%ebx 0xb71b693d : sub $0x24,%esp 0xb71b6940 : mov 0x30(%esp),%esi This is straight off the dvd. If I recompile using plain rpmbuild and no ~/.rpmrc I get a build with frame pointer. Valgrind is most unhappy with that, but it's easy to change valgrind to match: in valgrind/coregrind/m_stacktrace.c function get_StackTrace_wrk move the use_CF_info method before the frame-pointer method. I will file a bug with valgrind too. They should really provide a run-time method of choosing between the two methods. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.