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

List:       kdevelop-bugs
Subject:    [Bug 143512] Valgrind errors can appear in output window only after
From:       Arseniy Lartsev <receive-spam () yandex ! ru>
Date:       2007-03-29 12:28:24
Message-ID: 20070329122824.23978.qmail () ktown ! kde ! org
[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         




------- Additional Comments From receive-spam yandex ru  2007-03-29 14:28 -------
> Do you want KDevelop to immediately print the output from valgrind to the valgrind \
> outputwindow?

Yes I do.

> Is there an error in KDevelop?

Well, KDevelop doesn't print message immediately, so this is an error. The reason is \
that it expects a separator after the message but no separator is printed.

> And in does your last sentence indicate the KDevelop3.4 from svn doesn't have this \
> problem?

No, it indicates that problem _exists_ ("does exist" == "exsits").

This is a joint problem of KDevelop and Valgrind. There are two ways to fix it: \
either in KDevelop or in Valgrind. I wonder what way is better. Maybe it's easier to \
make Valgrind print separator than to make KDevelop detect end of message in \
different way. In the latter case, maybe I should re-post it as a wish for Valgrind?


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