From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH][gdb] Make INTERP_TUI's default ui_out the INTERP_CONSOLE ui_out
Date: Wed, 25 Sep 2019 08:36:00 -0000 [thread overview]
Message-ID: <20190925083642.GO4962@embecosm.com> (raw)
In-Reply-To: <f9ec5b8d-f1fe-fcc4-0974-cbd1cdca4817@suse.de>
* Tom de Vries <tdevries@suse.de> [2019-09-25 01:20:22 +0200]:
> On 24-09-19 19:31, Andrew Burgess wrote:
> > With this patch applied I see the fixed behaviour you describe at the
> > CLI, however, if I do:
> >
> > (gdb) define mybt
> > bt
> > end
> > (gdb) start
> > (gdb) set logging redirect on
> > (gdb) tui enable
> > (gdb) set logging on
> > (gdb) mybt
> >
> > The I see output appear on both the console and in the log file.
>
> I can't reproduce this. Are you sure you removed the gdb.txt file before
> starting gdb?
You're absolutely right, nothing goes to the log for `mybt`, this was
a silly mistake on my side. Apologies. However...
With tui enabled and logging on and redirect on, the 'bt' __does__
write to the log, while 'mybt' writes to the screen. This is the same
bug you're fixing for non-tui mode, correct? Any solution should
ideally address both cases, or at least be accompanied with an
explanation for why these problems are distinct and should be solved
separately.
Thanks,
Andrew
>
> Thanks,
> - Tom
next prev parent reply other threads:[~2019-09-25 8:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 9:58 Tom de Vries
2019-09-05 12:50 ` Tom de Vries
2019-09-24 15:24 ` [PING][PATCH][gdb] " Tom de Vries
2019-09-24 17:31 ` [PATCH][gdb] " Andrew Burgess
2019-09-24 23:20 ` Tom de Vries
2019-09-25 8:36 ` Andrew Burgess [this message]
2019-10-01 12:59 ` Tom de Vries
2019-10-03 10:01 ` [PATCH][gdb] Only force INTERP_CONSOLE ui_out for breakpoint commands in MI mode Tom de Vries
2019-10-03 12:11 ` Pedro Alves
2019-10-03 13:51 ` Tom de Vries
2019-10-03 14:02 ` Pedro Alves
2019-11-11 16:27 ` Joel Brobecker
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=20190925083642.GO4962@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
--cc=tom@tromey.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