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

List:       kde-bugs-dist
Subject:    [Bug 278972] New: Memcheck prints the wrong source file for certain
From:       <nn.dm55 () gmail ! com>
Date:       2011-07-31 21:36:16
Message-ID: bug-278972-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

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

           Summary: Memcheck prints the wrong source file for certain
                    functions.
           Product: valgrind
           Version: 3.5.0
          Platform: openSUSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: memcheck
        AssignedTo: jseward@acm.org
        ReportedBy: nn.dm55@gmail.com


Created an attachment (id=62400)
 --> (http://bugs.kde.org/attachment.cgi?id=62400)
Valgrind report run with "--leak-check=full
--log-file=supertuxkart-%p.valgrind"

Version:           3.5.0 (using KDE 4.6.0) 
OS:                Linux

Sometimes, Memcheck can't figure out what the correct file is. It prints the
name of some random header file instead of the correct source file.

Reproducible: Always

Steps to Reproduce:
Run Super Tux Kart with Memcheck.

Actual Results:  
The Alsa library function snd_pcm_area_copy is located in pcm.c at line 2653,
but Memcheck printed "string3.h:52".
In Super Tux Kart, the following function information was wrong:
DeviceManager::getConfigForGamepad is located in device_manager.c at line 183,
but Memcheck printed "basic_string.h:2369"
DeviceManager::addGamepad is in device_manager.c at line 228, but Memcheck
printed "stl_vector.h:749"

Expected Results:  
It should have printed "pcm.c:2653", "device_manager.c:183", and
"device_manager.c:228" instead.

This is with SVN version 9396 or so of Super Tux Kart.
See reports at lines 24, 68, and 137 of the attachment.
When using the Massif tool, it said "Malformed stack trace."

-- 
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]