From: Andreas Schwab <schwab@suse.de>
To: Chris Stankevitz <cstankevitz@toyon.com>
Cc: gdb@sourceware.org
Subject: Re: help me reduce typing when running gdb
Date: Wed, 28 Nov 2007 23:15:00 -0000 [thread overview]
Message-ID: <jed4tuq7wv.fsf@sykes.suse.de> (raw)
In-Reply-To: <474DC4C9.7000806@toyon.com> (Chris Stankevitz's message of "Wed\, 28 Nov 2007 11\:43\:05 -0800")
Chris Stankevitz <cstankevitz@toyon.com> writes:
> Hi, I often perform these steps:
>
> 1. bjam
> 2. gdb ./bin/debug/prog
> 3. r very long list of parameters that I hate typing
> 4. [lots of debugger commands like c, n, s, break, etc]
5. edit
6. make
7. run
8. goto 4
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-11-28 23:15 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 [this message]
2007-11-29 0:03 ` Tom Tromey
2007-11-29 11:21 ` Andrew STUBBS
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=jed4tuq7wv.fsf@sykes.suse.de \
--to=schwab@suse.de \
--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).