From: ISHWAR RATTAN <rattan@cps.cmich.edu>
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 15:13:35 -0400 [thread overview]
Message-ID: <Pine.GSO.4.61.0609141512300.3865@cps204.cps.cmich.edu> (raw)
In-Reply-To: <dac0a5820609141059g6d97b495pee0f2d06d62a0452@mail.gmail.com>
I had looked through /sys/doc/acid.* and was unable to find
the information there. Maybe it is something trivial :-(
-ishwar
On Thu, 14 Sep 2006, Tharaneedharan Vilwanathan wrote:
> Acid Tutorial by Tad Hunt also may be useful. I see it in
> /doc/acidtut.pdf in Inferno release but I couldnt find a web link.
>
> regards
> dharani
>
> On 9/14/06, Skip Tavakkolian <9nut@9netics.com> 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
>>
>>
>
next prev parent reply other threads:[~2006-09-14 19:13 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 [this message]
2006-09-14 21:49 ` Tharaneedharan Vilwanathan
2006-09-14 20:24 ` ISHWAR RATTAN
2006-09-14 20:40 ` Axel Belinfante
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=Pine.GSO.4.61.0609141512300.3865@cps204.cps.cmich.edu \
--to=rattan@cps.cmich.edu \
--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).