From: Andrew STUBBS <andrew.stubbs@st.com>
To: Chris Stankevitz <cstankevitz@toyon.com>
Cc: gdb@sourceware.org
Subject: Re: help me reduce typing when running gdb
Date: Thu, 29 Nov 2007 11:21:00 -0000 [thread overview]
Message-ID: <474EA0B4.2000801@st.com> (raw)
In-Reply-To: <474DC4C9.7000806@toyon.com>
Chris Stankevitz wrote:
> Can anyone recommend a way to streamline this process? Particularly
> Step 3 and Step 5. In MSVC, steps 1-3 is one keystroke (F5) and step 5
> is two (SHIFT-F5, F5).
The TUI has some single key commands for stepping and such - I use those
a lot. The source view is very nice to have too.
You might also like to check out the history save feature. I have these
lines in my .gdbinit:
set history expansion
set history save on
Basically it just means that, when you start a new GDB session in the
same directory as a previous one, you can hit 'up' and the commands from
your last session are still there.
Andrew
prev parent reply other threads:[~2007-11-29 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 19:43 Chris Stankevitz
2007-11-28 19:57 ` ramana.radhakrishnan
2007-11-28 20:22 ` Michael Snyder
2007-11-28 21:33 ` Gordon Prieur
2007-11-28 22:55 ` Chris Stankevitz
2007-11-28 23:15 ` Andreas Schwab
2007-11-29 0:03 ` Tom Tromey
2007-11-29 11:21 ` Andrew STUBBS [this message]
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=474EA0B4.2000801@st.com \
--to=andrew.stubbs@st.com \
--cc=cstankevitz@toyon.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).