Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Arjan van Dijk <a.vandijk@phys.uu.nl>
To: gdb@sources.redhat.com
Subject: Re: problem setting displays
Date: Fri, 06 Sep 2002 06:43:00 -0000	[thread overview]
Message-ID: <v03130302b99e5fab1ba8@[131.211.32.140]> (raw)
In-Reply-To: <20020906130835.GA6986@nevyn.them.org>

>That's not how you do it.  You run until you are in MAIN__ and "display
>x".  Does that work?






No. The session that I showed only halted in MAIN__, so your condition was
satisfied and none of the displays that I tried to set were accepted.
Moreover, when I asked gdb to

   display MAIN__::i
   display MAIN__::x

before I said

   run

then all went ok. I had my watches every time gdb halted. As you may have
seen, no new watches were accepted once I commanded gdb to run. On 5.2.1 I
could get the watches after I reloaded the executable. On the Linux box
with gdb 5.0.x this did not work.

How can I have the value of a variable printed just once when program
execution halts? This instead of using "display". Maybe I could use such a
command. Would mean that I have to call all variables that I want to watch
every time the program halts, but until so far the 'display' command does
not seem to work.

Arjan


Arjan van Dijk
Institute for Marine and Atmospheric Research Utrecht
Faculty of Physics and Astronomy
Utrecht University
Princetonplein 5
NL - 3584 CC  Utrecht
The Netherlands

phone: +31 30 2532815
fax:   +31 30 2543163
e-mail: mailto:A.vanDijk@phys.uu.nl
homepage: http://www.phys.uu.nl/~vndijk



  reply	other threads:[~2002-09-06 13:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-06  4:06 Arjan van Dijk
2002-09-06  6:08 ` Daniel Jacobowitz
2002-09-06  6:43   ` Arjan van Dijk [this message]
2002-09-12 12:17     ` Andrew Cagney
2002-09-13  0:45       ` Arjan van Dijk

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='v03130302b99e5fab1ba8@[131.211.32.140]' \
    --to=a.vandijk@phys.uu.nl \
    --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