From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [patchv2 8/11] TUI: source "file" -> "fullname"
Date: Thu, 07 Feb 2013 19:48:00 -0000 [thread overview]
Message-ID: <CADPb22TWiwakKhfVk7ntSnHvv+aG7ePuwuxjysDvdNwyiWT2tw@mail.gmail.com> (raw)
In-Reply-To: <20130127223625.GI15252@host2.jankratochvil.net>
On Sun, Jan 27, 2013 at 2:36 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> Hi,
>
> this is a new part in this v2 series.
>
> It was tested current "gdb -tui" is really incorrect and it gets fixed by this
> patch:
> cd gdb.linespec/
> cd base/one/
> g++ -o ../../1.o -c thefile.cc -Wall -g
> cd ../two
> g++ -o ../../2.o -c thefile.cc -Wall -g
> cd ../..
> g++ -o 0 lspec.cc -Wall -g 1.o 2.o
> ../../gdb-tuiN -tui ./0
> ../../gdb-tuiY -tui ./0
> b m
> b n
> r
> c
> With this patch GDB displays the first thefile.cc for m() and the second
> thefile.cc for n(); without this patch it forgot to display n().
>
> It expects that if !ui_out_is_mi_like_p and !ui_source_list it is really TUI
> and no other uiout interface; I hope it is safe assumption and there will be
> no new interfaces besides current CLI + TUI + MI.
Re: "no new interfaces": Perhaps not immediately relevant here, but I
think it's something we need to keep in mind.
I gather people are thinking of putting GUI-like things on top of gdb
via the Python API.
So it's really CLI + TUI + MI + potentially-Python.
next prev parent reply other threads:[~2013-02-07 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 22:36 Jan Kratochvil
2013-02-03 16:17 ` [commit] " Jan Kratochvil
2013-02-07 19:48 ` Doug Evans [this message]
2013-02-07 19:54 ` Jan Kratochvil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADPb22TWiwakKhfVk7ntSnHvv+aG7ePuwuxjysDvdNwyiWT2tw@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox