Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
To: james osburn <jjosburn@hotmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: tracing ( was Re: what are gdbstubs?)
Date: Thu, 24 Mar 2005 23:59:00 -0000	[thread overview]
Message-ID: <4243541A.2010300@codito.com> (raw)
In-Reply-To: <BAY13-F4029FB867B3C92AF7B57ACD8400@phx.gbl>

james osburn wrote:
> no actually i am very very new to using
> gdb so no i didnt know about scripting the
> break points. how does that work?
> jim

Its like this  . Look at the commands command for gdb .

So at each program point if you specify the variables of 
interest for you, you could generate the following set of 
commands for the same.

break <location>
commands
  > p <variable>
  > p $eax
  > p $ebx
  > end


etc.

or you could use the display command for each of the 
variables that you wish to see and then single step as many 
instructions / source lines as you want.


cheers
Ramana


-- 
Ramana Radhakrishnan
GNU Tools
codito ergo sum (www.codito.com)


  reply	other threads:[~2005-03-24 23:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 16:58 what are gdbstubs? james osburn
2005-03-24 17:08 ` Ramana Radhakrishnan
2005-03-24 22:55   ` james osburn
2005-03-24 23:08     ` Ramana Radhakrishnan
2005-03-24 23:12       ` james osburn
2005-03-24 23:15         ` Ramana Radhakrishnan
2005-03-24 23:25           ` tracing ( was Re: what are gdbstubs?) james osburn
2005-03-24 23:44             ` Ramana Radhakrishnan
2005-03-24 23:47               ` Daniel Jacobowitz
2005-03-24 23:48               ` james osburn
2005-03-24 23:59                 ` Ramana Radhakrishnan [this message]
2005-03-25  0:09                   ` Ramana Radhakrishnan

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=4243541A.2010300@codito.com \
    --to=ramana.radhakrishnan@codito.com \
    --cc=gdb@sources.redhat.com \
    --cc=jjosburn@hotmail.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