From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb@sourceware.org
Subject: Expected behaviour of 'set width XX'
Date: Thu, 20 Jul 2017 07:49:00 -0000 [thread overview]
Message-ID: <20170720074853.GL27353@embecosm.com> (raw)
I have a question about the expected behaviour of set width. I'm
going to use 'set width 10' in the example below, I know 10 probably
isn't a very useful width, but I see the same behaviour for larger
widths.
In the pictures below I'm using "|" to denote the left edge of the
terminal, and "^" to indicate where the cursor is in the line above
(the line with the actual "^" does not exist yet).
So, I start up gdb and I see this:
|(gdb)
| ^
Then I set the desired width,
|(gdb) set width 10
|(gdb)
| ^
Now I enter 3 "x"s.
|(gdb) xxx
| ^
you'll notice that including the prompt, single space, and xxx I'm now
ready to fill character 10, so, I add 1 more x:
|(gdb) xxxx
|^
Notice that the cursor has wrapper back to the first character on the
line. After this I enter 9 "y"s:
|yyyyyyyyy
| ^
Yeah.... and one more "y":
|yyyyyyyyyy
|^
And we're back to the beginning of the line again.
My expectation was that after all the "x"s and "y"s, I would have had
this situation:
|(gdb) xxxx
|yyyyyyyyyy
|
|^
So a 10 character wide block of text on the left of my N wide
terminal.
So, my question: Is the current gdb behaviour the expected behaviour?
If it is the expected behaviour then how is this useful?
Thanks,
Andrew
next reply other threads:[~2017-07-20 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 7:49 Andrew Burgess [this message]
2017-07-20 8:17 ` Andreas Schwab
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=20170720074853.GL27353@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb@sourceware.org \
/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