public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Alexander von Below <below@mac.com>
To: gdb@sources.redhat.com
Subject: Startup Scripts and Duplicates in the History
Date: Wed, 14 Sep 2005 12:24:00 -0000	[thread overview]
Message-ID: <1EFA79A4-2799-4433-A7D2-DF3A5C0054CD@mac.com> (raw)

Hello List,

maybe I did not google hard enough, but I could not find an answer to  
the following, hopefully trivial question:

1) I would like to "optimize" my workflow, and have a script executed  
everytime I start gdb from a certain directory, or in a certain way.  
Namely, what the script should do is:

add-symbol-file com.my.driver.sym  (gdb also always wants to confirm  
this, can I disable this confirmation?)
target remote-kdp

2) Is there a way to not add duplicates to the gdb history? Every  
"next" or "cont" is recorded, which seems unnecessary. My usual  
debugging session involves setting some breakpoints, a lot of next  
and cont, and print. And I would like to quickly step over the  
"next"s to recall the break point settings in the next session


Thanks for you help

Alex

             reply	other threads:[~2005-09-14 12:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14 12:24 Alexander von Below [this message]
2005-09-14 13:28 ` Dave Korn
2005-09-14 13:34   ` Bob Rossi

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=1EFA79A4-2799-4433-A7D2-DF3A5C0054CD@mac.com \
    --to=below@mac.com \
    --cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).