[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: [Bug 143512] New: Valgrind errors can appear in output window only
From: preved <receive-spam () yandex ! ru>
Date: 2007-03-27 12:27:31
Message-ID: 20070327142729.143512.receive-spam () yandex ! ru
[Download RAW message or body]
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=143512
Summary: Valgrind errors can appear in output window only after
program exits
Product: kdevelop
Version: unspecified
Platform: SuSE RPMs
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: valgrind integration
AssignedTo: kdevelop-bugs kdevelop org
ReportedBy: receive-spam yandex ru
Version: (using KDE KDE 3.5.5)
Installed from: SuSE RPMs
Compiler: gcc 4.1.2
OS: Linux
Consider program like this:
#include <stdio.h>
int main(int argc, char *argv[])
{
bool *b = new bool;
if (*b)
printf("Preved\n");
while (1) ;
return 0;
}
If we do Debug - Valgrind Memory Leak Check in KDevelop main menu for this program, we will only see \
"Memcheck, a memory error detector blah blah blah" in Valgrind output. Error message "Conditional jump or \
move depends on uninitialised value(s)" (which is written by valgrind when program reaches line "if \
(*b)") will be seen only after we terminate the program by choosing Build - Stop in main menu. The reason \
is that valgrind does not print separator ("==NNNNN==" without any message) after error message so \
KDevelop thinks message isn't finished. The easiest solution is to make valgrind write a separator after \
each error message (not before the next message like it does now, BTW extra separators don't seem to be a \
problem).
This problem does exist in the most recent SVN versions of KDevelop 3.4 and valgrind 3.3.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic