https://bugs.kde.org/show_bug.cgi?id=384791
--- Comment #11 from Jaka Kranjc ---
That could explain it, but:
- stdout is supposed to be line-buffered, not fully buffered
- why doesn't it behave the same when ran from konsole directly?
I can add a setvbuf call that will likely fix it, but I'd lik
https://bugs.kde.org/show_bug.cgi?id=384791
--- Comment #10 from Milian Wolff ---
Doing that for the python debugger may be OK, but for C/C++ there's no such
option.
@Jaka Kranjc: Your code in StdioLogger::print is doing:
fprintf(stdout, "%s", message);
stdout is buffered, this is not KDevelop
https://bugs.kde.org/show_bug.cgi?id=384791
--- Comment #9 from Gaël de Chalendar (aka Kleag) ---
(In reply to Gaël de Chalendar (aka Kleag) from comment #8)
> On my side, the problem appear when running python code. I just noticed that
> output of my python script is also buffered when running i
https://bugs.kde.org/show_bug.cgi?id=384791
--- Comment #8 from Gaël de Chalendar (aka Kleag) ---
On my side, the problem appear when running python code. I just noticed that
output of my python script is also buffered when running in a console like
that:
$ python tracenn.py 2>&1 | tee output.lo
https://bugs.kde.org/show_bug.cgi?id=384791
--- Comment #7 from Gaël de Chalendar (aka Kleag) ---
I would mark this bug as important instead of normal. It is quite a show
stopper for using kdevelop for debugging, dont't you think.
Note that I noticed just after submitting #427128 that it does no
https://bugs.kde.org/show_bug.cgi?id=384791
Francis Herne changed:
What|Removed |Added
CC||kle...@gmail.com
--- Comment #6 from Francis He
https://bugs.kde.org/show_bug.cgi?id=384791
--- Comment #5 from Jaka Kranjc ---
Ok, finally took the time to investigate. Our logging does some string
construction, but everything ends up being printed by fprintf. It's all in this
file:
https://github.com/gemrb/gemrb/blob/master/gemrb/core/System
https://bugs.kde.org/show_bug.cgi?id=384791
Kevin Funk changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=384791
--- Comment #3 from Jaka Kranjc ---
They are newline terminated, but maybe multiline strings (these dumps are long)
end up treated differently. I'll take a look.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384791
--- Comment #2 from Kevin Funk ---
@Jaka: Does your program log to stdout without printing a newline?
I think if it *does* print a newline, then you shouldn't actually notice the
internal buffering -- we're actually processing output at least every 50
https://bugs.kde.org/show_bug.cgi?id=384791
--- Comment #1 from Kevin Funk ---
For the record, relevant code is in
kdevelop.git:kdevplatform/outputview/outputmodel.cpp.
If you want to investigate the issue yourself, please have a look at further
instructions at:
https://www.kdevelop.org/contri
11 matches
Mail list logo
