This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [pushed] Fix PR tui/21216: TUI line breaks regression


On Fri, 10 Mar 2017 19:17:20 +0100, Pedro Alves wrote:
> How you love pulling things out of context.  

Because everything is interconnected.


> Whatever testing you think would be appropriate for testing TUI/ncurses
> _output_ in your project, we can consider for GDB too.  If you have ideas
> for that, please share them.

I do not think a front end UI really needs any testsuite as it is a trivial
code (in a proper language and with proper API - not MI; MI is not API and not
proper).  That is not the case of a front end intertwingled into GDB core.

Besides that maybe one could fix a TUI frontend for the testsuite purposes.
I have no idea how much usable ncurses is with "dumb":
$ TERM=dumb gdb -tui
Cannot enable the TUI: terminal doesn't support cursor addressing [TERM=dumb]


> > and you were right, there are other debuggers which
> > already do it the right way.
> 
> I don't think I ever said such a thing.

You said something different although IMO with the same practical result.
This text from an internal list but I do not find that too secret:

On Fri, 26 Jun 2015 18:44:11 +0200, Pedro Alves wrote:
# Basically you're saying we should rewrite the whole CLI from scratch.
# And it basically seems like writing a _different_ debugger from
# scratch to me.


Jan


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]