[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 278972] Memcheck prints the wrong source file for certain
From:       Philippe Waroquiers <philippe.waroquiers () skynet ! be>
Date:       2011-08-01 9:43:46
Message-ID: E1Qnp2I-00028r-6E () bugs ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=278972


Philippe Waroquiers <philippe.waroquiers@skynet.be> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |philippe.waroquiers@skynet.
                   |                            |be




--- Comment #5 from Philippe Waroquiers <philippe waroquiers skynet be>  2011-08-01 09:43:45 ---
(In reply to comment #3)
> Any way to make it show the source file which memcpy was inlined into instead
> of the function definition?
It looks like gdb can do a better stacktrace than Valgrind.
The below shows the stack trace produced by a gdb attached to the
Valgrind gdbserver, followed by the stacktrace produced by Valgrind
(using a just locally added new "valgrind monitor command". I will submit
a patch on Valgrind to add this monitor command).

So, the information is for sure available to build the stacktrace
for inlined function (as gdb can do it). But enhancing Valgrind stacktrace
to show that might be tricky.

(gdb) bt
#0  0x06d7be54 in printf () from /lib/libc.so.6
#1  0x080483d0 in fun_inline (argc=1, argv=0xfee18d04 "O\220\341\376")
    at inl.h:3
#2  main (argc=1, argv=0xfee18d04 "O\220\341\376") at inl.c:7
(gdb) monitor v.info scheduler

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable
==29435==    at 0x6D7BE54: printf (in /lib/libc-2.5.so)
==29435==    by 0x80483CF: main (inl.h:3)

(gdb)

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]