9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] OT: Acid question?
Date: Thu, 14 Sep 2006 22:40:27 +0200	[thread overview]
Message-ID: <200609142040.k8EKeSE15785@demeter.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Thu, 14 Sep 2006 16:24:15 -0400." <Pine.GSO.4.61.0609141622110.3928@cps204.cps.cmich.edu>

you may want to try using the -N flag of 8c
(I guess you did not, and thus your variables were optimized away)

of course I may be completely wrong - trying to learn something here too...

Axel

> acid: *(main:a\D)
> 
> produces:
> <stdin:23:(error) colon: local variable not found
> 
> -ishwar
> 
> 
> On Thu, 14 Sep 2006, Skip Tavakkolian wrote:
> 
> > *(main:a\D)
> >
> > /sys/doc/acid.ps
> > /sys/doc/acidpaper.ps
> >
> >> I am trying to learn how to use acid for source
> >> level debugging using the built-in functions. I waould like
> >> to know how to display/exmine the varibales used in the
> >> program. Sample code for context:
> >>   void main()
> >>   {
> >>     int a, b, c;
> >>     a = 12;
> >>     b = 21;
> >>     c = a + b;
> >>     print("c: %d\n", c);
> >>     exits(nil);
> >>   }
> >>
> >>   program is compiled and acid is called on the image:
> >>   acid: new()
> >>   ..
> >>   acid: bpset(print)
> >>   ..
> >>   acid: next()
> >>   ..
> >>   at this point a = 12 has been executed. How to examine
> >>   the value in acid?
> >>
> >> -ishwar
> >


  reply	other threads:[~2006-09-14 20:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14 14:41 ISHWAR RATTAN
2006-09-14 16:33 ` Skip Tavakkolian
2006-09-14 17:59   ` Tharaneedharan Vilwanathan
2006-09-14 19:13     ` ISHWAR RATTAN
2006-09-14 21:49       ` Tharaneedharan Vilwanathan
2006-09-14 20:24   ` ISHWAR RATTAN
2006-09-14 20:40     ` Axel Belinfante [this message]
2006-09-14 20:55       ` Gabriel Diaz
2006-09-14 21:06       ` ISHWAR RATTAN
2006-09-14 23:56 ` Russ Cox
2006-09-15  1:08   ` Benn Newman

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=200609142040.k8EKeSE15785@demeter.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).