<div dir="ltr"><p dir="ltr">Hi,</p>
<p>In fact I know this issue. It's because debugger console stream was redirected to application output in commit 609bacd7 (by Kevin XD), so I tried to keep the same behavior when cleaning up. Apparently there's something I missed.</p><p>We should rethink what kind of outputs we want to show in Debug view.<br></p><p>Currently, the outputs are routed like:</p><div class="inbox-inbox-well inbox-inbox-well-small inbox-inbox-well-white inbox-inbox-pre">
<div class="inbox-inbox-text" style="font-family:monospace"><ol><li style="font-weight:normal;vertical-align:top" id="inbox-inbox-line-1"><div style="font:1em/1.2em monospace;margin:0px;padding:0px;background:transparent none repeat scroll 0% 0%;vertical-align:middle">- Application output -> debugger target stream -> applicationOutput signal -> Debug View</div></li><li style="font-weight:normal;vertical-align:top" id="inbox-inbox-line-2"><div style="font:1em/1.2em monospace;margin:0px;padding:0px;background:transparent none repeat scroll 0% 0%;vertical-align:middle">- Internal command line -> internalCommandOutput signal -> Debug View, GDB Console</div></li><li style="font-weight:normal;vertical-align:top" id="inbox-inbox-line-3"><div style="font:1em/1.2em monospace;margin:0px;padding:0px;background:transparent none repeat scroll 0% 0%;vertical-align:middle">-
Internal command output part 1 -> debugger console stream ->
internalCommandOutput signal -> Debug View, GDB Console</div></li><li style="font-weight:normal;vertical-align:top" id="inbox-inbox-line-4"><div style="font:1em/1.2em monospace;margin:0px;padding:0px;background:transparent none repeat scroll 0% 0%;vertical-align:middle">-
Internal command output part 2 -> debugger result record ->
internalCommandOutput signal -> Debug View, GDB Console</div></li><li style="font-weight:bold;vertical-align:top" id="inbox-inbox-line-5"><div style="font:1em/1.2em monospace;margin:0px;padding:0px;background:transparent none repeat scroll 0% 0%;vertical-align:middle">- User command line -> userCommandOutput signal -> GDB Console</div></li><li style="font-weight:normal;vertical-align:top" id="inbox-inbox-line-6"><div style="font:1em/1.2em monospace;margin:0px;padding:0px;background:transparent none repeat scroll 0% 0%;vertical-align:middle">- User command output -> debugger console stream -> userCommandOutput signal -> GDB Console</div></li><li style="font-weight:normal;vertical-align:top" id="inbox-inbox-line-7"><div style="font:1em/1.2em monospace;margin:0px;padding:0px;background:transparent none repeat scroll 0% 0%;vertical-align:middle">- Debugger internal log -> debugger log stream -> debuggerInternalOutput signal -> GDB Console</div></li></ol></div>
</div><p>Previous behavior was:</p><div class="inbox-inbox-well inbox-inbox-well-small inbox-inbox-well-white inbox-inbox-pre">
<div class="inbox-inbox-text" style="font-family:monospace"><ol><li style="font-weight:normal;vertical-align:top" id="inbox-inbox-line-1"><div style="font:1em/1.2em monospace;margin:0px;padding:0px;background:transparent none repeat scroll 0% 0%;vertical-align:middle">- Application output -> debugger target stream -> applicationOutput signal -> Debug View</div></li><li style="font-weight:normal;vertical-align:top" id="inbox-inbox-line-2"><div style="font:1em/1.2em monospace;margin:0px;padding:0px;background:transparent none repeat scroll 0% 0%;vertical-align:middle">- Internal command line -> internalCommandOutput signal -> GDB Console</div></li><li style="font-weight:normal;vertical-align:top" id="inbox-inbox-line-3"><div style="font:1em/1.2em monospace;margin:0px;padding:0px;background:transparent none repeat scroll 0% 0%;vertical-align:middle">- Internal command output part 1 -> debugger console stream -> applicationOutput signal -> Debug View</div></li><li style="font-weight:normal;vertical-align:top" id="inbox-inbox-line-4"><div style="font:1em/1.2em monospace;margin:0px;padding:0px;background:transparent none repeat scroll 0% 0%;vertical-align:middle">- Internal command output part 2 -> debugger result record -> internalCommandOutput signal -> GDB Console</div></li><li style="font-weight:bold;vertical-align:top" id="inbox-inbox-line-5"><div style="font:1em/1.2em monospace;margin:0px;padding:0px;background:transparent none repeat scroll 0% 0%;vertical-align:middle">- User command line -> userCommandOutput signal -> GDB Console</div></li><li style="font-weight:normal;vertical-align:top" id="inbox-inbox-line-6"><div style="font:1em/1.2em monospace;margin:0px;padding:0px;background:transparent none repeat scroll 0% 0%;vertical-align:middle">- User command output -> debugger console stream -> userCommandOutput signal -> GDB Console</div></li><li style="font-weight:normal;vertical-align:top" id="inbox-inbox-line-7"><div style="font:1em/1.2em monospace;margin:0px;padding:0px;background:transparent none repeat scroll 0% 0%;vertical-align:middle">- Debugger internal log -> debugger log stream -> debuggerInternalOutput signal -> GDB Console</div></li></ol></div>
</div><p>In my opinion, we really should only have application output routed to the Debug view. What do you think?</p><p>Cheers,</p><p>Peifeng Yu<br></p><br><div class="gmail_quote"><div dir="ltr">On Tue, Jul 26, 2016, 03:12 Jeremy Murphy <<a href="mailto:jeremy.william.murphy@gmail.com" target="_blank">jeremy.william.murphy@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I just reverted to 4.90.91 and the output is quite different. I've completely abbreviated the actual program output and some verbose templates in the line where it hits a breakpoint:<div><br></div><div><br></div><div></div></div><div dir="ltr"><div><div>GNU gdb (Gentoo 7.11.1 vanilla) 7.11.1</div><div>Copyright (C) 2016 Free Software Foundation, Inc.</div><div>License GPLv3+: GNU GPL version 3 or later <<a href="http://gnu.org/licenses/gpl.html" target="_blank">http://gnu.org/licenses/gpl.html</a>></div><div>This is free software: you are free to change and redistribute it.</div><div>There is NO WARRANTY, to the extent permitted by law. Type "show copying"</div><div>and "show warranty" for details.</div><div>This GDB was configured as "x86_64-pc-linux-gnu".</div><div>Type "show configuration" for configuration details.</div><div>For bug reporting instructions, please see:</div><div><<a href="https://bugs.gentoo.org/" target="_blank">https://bugs.gentoo.org/</a>>.</div><div>Find the GDB manual and other documentation resources online at:</div><div><<a href="http://www.gnu.org/software/gdb/documentation/" target="_blank">http://www.gnu.org/software/gdb/documentation/</a>>.</div><div>For help, type "help".</div><div>Type "apropos word" to search for commands related to "word".</div></div></div><div dir="ltr"><div><div>Signal Stop<span style="white-space:pre-wrap"> </span>Print<span style="white-space:pre-wrap"> </span>Pass to program<span style="white-space:pre-wrap"> </span>Description</div><div>SIG32 No<span style="white-space:pre-wrap"> </span>No<span style="white-space:pre-wrap"> </span>Yes<span style="white-space:pre-wrap"> </span>Real-time event 32</div><div>Signal Stop<span style="white-space:pre-wrap"> </span>Print<span style="white-space:pre-wrap"> </span>Pass to program<span style="white-space:pre-wrap"> </span>Description</div><div>SIG41 No<span style="white-space:pre-wrap"> </span>No<span style="white-space:pre-wrap"> </span>Yes<span style="white-space:pre-wrap"> </span>Real-time event 41</div><div>Signal Stop<span style="white-space:pre-wrap"> </span>Print<span style="white-space:pre-wrap"> </span>Pass to program<span style="white-space:pre-wrap"> </span>Description</div><div>SIG42 No<span style="white-space:pre-wrap"> </span>No<span style="white-space:pre-wrap"> </span>Yes<span style="white-space:pre-wrap"> </span>Real-time event 42</div><div>Signal Stop<span style="white-space:pre-wrap"> </span>Print<span style="white-space:pre-wrap"> </span>Pass to program<span style="white-space:pre-wrap"> </span>Description</div><div>SIG43 No<span style="white-space:pre-wrap"> </span>No<span style="white-space:pre-wrap"> </span>Yes<span style="white-space:pre-wrap"> </span>Real-time event 43</div><div>[Thread debugging using libthread_db enabled]</div><div>Using host libthread_db library "/lib64/libthread_db.so.1".</div><div><br></div><div>---- my program output ---</div><div><br></div><div>Breakpoint 1, footprinter::create_split_segments<...templates, templates, templates...>../footprinter.hpp:146<br></div><div>146<span style="white-space:pre-wrap"> </span> vector<segment_data<double>> segments;</div></div><div><br></div><div><br></div><div>Cheers.</div></div><div dir="ltr"><div><br></div><div>Jeremy</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 26 July 2016 at 16:02, Jeremy Murphy <span dir="ltr"><<a href="mailto:jeremy.william.murphy@gmail.com" target="_blank">jeremy.william.murphy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi everyone,<div><br></div><div>I'm loving KDevelop 5.0 alpha/beta/gamma whatever it is up to. :)</div><div><br></div><div>Except recently, it started sending verbose GDB output to the Debug view (along with the actual program output that I would expect) like so:</div><div><br></div><div><br></div><div><div>(gdb) 1-gdb-show version</div><div>GNU gdb (Gentoo 7.11.1 vanilla) 7.11.1</div><div>Copyright (C) 2016 Free Software Foundation, Inc.</div><div>License GPLv3+: GNU GPL version 3 or later <<a href="http://gnu.org/licenses/gpl.html" target="_blank">http://gnu.org/licenses/gpl.html</a>></div><div>This is free software: you are free to change and redistribute it.</div><div>There is NO WARRANTY, to the extent permitted by law. Type "show copying"</div><div>and "show warranty" for details.</div><div>This GDB was configured as "x86_64-pc-linux-gnu".</div><div>Type "show configuration" for configuration details.</div><div>For bug reporting instructions, please see:</div><div><<a href="https://bugs.gentoo.org/" target="_blank">https://bugs.gentoo.org/</a>>.</div><div>Find the GDB manual and other documentation resources online at:</div><div><<a href="http://www.gnu.org/software/gdb/documentation/" target="_blank">http://www.gnu.org/software/gdb/documentation/</a>>.</div><div>For help, type "help".</div><div>Type "apropos word" to search for commands related to "word".</div><div>1^done</div><div>(gdb) 2-gdb-set width 0</div><div>2^done</div><div><br></div><div>---8<--- ~200 lines of output ---8<---</div><div><br></div><div>(gdb) 129-var-create --thread 1 --frame 0 var113 @ "typename"</div><div>129^error,msg="-var-create: unable to create variable object"</div><div>(gdb) 130-var-create --thread 1 --frame 0 var114 @ "back_inserter"</div><div>130^error,msg="-var-create: unable to create variable object"</div></div><div><br></div><div><br></div><div>It sends the messages when I run debug, obviously, but also when I mouse over variables as the last couple of lines are an example of.</div><div><br></div><div>I'm using the latest releases of just about everything, which at the moment is GDB 7.11.1, Qt 5.6.1, Frameworks 5.24.0, Plasma 5.7.2, and tip of the 5.0 branch for KDevelop and KDevPlatform.</div><div><br></div><div>Is this a known issue or am I the lucky discoverer? I can't recall exactly when I first noticed it, sorry, but it must have been recently.</div><div><br></div><div>Thanks, cheers.</div><span><font color="#888888"><div><br></div><div>Jeremy</div><div><br></div></font></span></div>
</blockquote></div><br></div>
_______________________________________________<br>
KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kde.org" target="_blank">KDevelop-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kdevelop-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/kdevelop-devel</a><br>
</blockquote></div></div>