number of scrollback lines in "run" and "debug" windows

Chris Bruner cbruner at quadro.net
Fri Apr 13 23:20:14 UTC 2012


I didn't know kdevelop was meant to train people in 'proper' debugging 
procedures.  Just because you've never had the need doesn't mean that it 
isn't there. There may be an extreme corner case, that he doesn't know 
the cause for. It happens every 60,000 lines of debug info or so. By 
having the info available he may be able to narrow the parameters down.

However I will agree that this type of debugging inside an ide seems 
strange. I'd use a command line an pipe it through grep.

On 4/13/2012 5:58 PM, Michael George Hart wrote:
> You are missing the point; to track to 1 billion lines of debugging 
> output encourages this and other people to develop very poor debugging 
> skills. The standard debugger that comes with LINUX has a tremendous 
> number of features that should prevent someone from the need to dump 
> out a billion lines of junk.
>
> The dumping of 1 billion lines anything is not debugging; it is at 
> best a scatter shot approach understanding a problem... Dump enough 
> data and hope to see a pattern.
>
> I would suggest this person get a full grasps of how there code is 
> suppose work rather than dump the entire run then carefully use 
> features of the debugger stop where their deviation from expected 
> values...
>
> From my point of view 50,000 lines very generous
>
>
> I, the unwilling, was lead by the unqualified, to do the unbelievable 
> for so long with so little, that I attempted the impossible with nothing
>
> Sent from my iPad
>
> On Apr 13, 2012, at 5:28 PM, Alireza Haghdoost <haghdoost at gmail.com 
> <mailto:haghdoost at gmail.com>> wrote:
>
>> It would be great If we can use redirection operator (>) in the 
>> kdevelop 4 run command.
>>
>> On Fri, Apr 13, 2012 at 12:54, Mahmood Naderan <mahmood.nt at gmail.com 
>> <mailto:mahmood.nt at gmail.com>> wrote:
>>
>>     my simulation logs is very lengthy running for 1B events
>>
>>     On 4/13/12, Michael George Hart <michael.george.hart at gmail.com
>>     <mailto:michael.george.hart at gmail.com>> wrote:
>>     > Now for an opinion that you might find unproductive.
>>     >
>>     > If you need, in my humble opinion, need more than a few
>>     hundreds lines of
>>     > output in you run debug window, I recommend you seriously step
>>     back and
>>     > asses you debugging style.
>>     >
>>     > If you are debugging a server product, running as a damon etc.
>>     that is why
>>     > people run servers in debug mode watching the logs of a server.
>>     >
>>     > 50,000 lines seems very, very generous. Could you justify why
>>     you would need
>>     > more than that. I have more than 30 years software development
>>     experience an
>>     > I am trying to discover what could you possibly need more than
>>     the very
>>     > generous 50,000 lines.
>>     >
>>     > Michael
>>     >
>>     > I, the unwilling, was lead by the unqualified, to do the
>>     unbelievable for so
>>     > long with so little, that I attempted the impossible with nothing
>>     >
>>     > Sent from my iPad
>>     >
>>     > On Apr 13, 2012, at 11:33 AM, Milian Wolff <mail at milianw.de
>>     <mailto:mail at milianw.de>> wrote:
>>     >
>>     >> On Thursday 12 April 2012 18:24:20 Mahmood Naderan wrote:
>>     >>> Hi,
>>     >>> Is it possible to increase the number of output lines in
>>     "run" and
>>     >>> "debug" window? Currently they show 50,000 lines.
>>     >>
>>     >> no it's not possible without changing the sources.
>>     >>
>>     >> bye
>>     >> --
>>     >> Milian Wolff
>>     >> mail at milianw.de <mailto:mail at milianw.de>
>>     >> http://milianw.de
>>     >> _______________________________________________
>>     >> kdevelop mailing list
>>     >> kdevelop at kdevelop.org <mailto:kdevelop at kdevelop.org>
>>     >> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop
>>     >
>>     > _______________________________________________
>>     > kdevelop mailing list
>>     > kdevelop at kdevelop.org <mailto:kdevelop at kdevelop.org>
>>     > https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop
>>     >
>>
>>
>>     --
>>     --
>>     // Naderan *Mahmood;
>>
>>     _______________________________________________
>>     kdevelop mailing list
>>     kdevelop at kdevelop.org <mailto:kdevelop at kdevelop.org>
>>     https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop
>>
>>
>> _______________________________________________
>> kdevelop mailing list
>> kdevelop at kdevelop.org <mailto:kdevelop at kdevelop.org>
>> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop
>
>
> _______________________________________________
> kdevelop mailing list
> kdevelop at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop


-- 
Chris Bruner

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop/attachments/20120413/ae7b3118/attachment.html>


More information about the KDevelop mailing list