From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,2eaa2dcf836e629b,start
X-Google-Attributes: gid103376,public
From: "Corey Ashford" <corSPAMey@rational.com>
Subject: Re: Using the SDS SingleStep Debugging Suite for Ada???
Date: 1998/07/18
Message-ID: <6orn9s$1nh$1@usenet.rational.com>#1/1
X-Deja-AN: 372787860
References: <1998071902425500.WAA29899@ladder03.news.aol.com>
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Organization: Rational Software
Newsgroups: comp.lang.ada
Date: 1998-07-18T00:00:00+00:00
List-Id: <comp.lang.ada>


Escheria wrote in message <1998071902425500.WAA29899@ladder03.news.aol.com>...
>I'd like to be able to use the SDS SingleStep debugging suite for code compiled
>with the Rational Ada compiler. The SingleStep debugger is intended only for C,
>C++, and Assembly code, however I'm presently able to get it to work for Ada
>with limited capabilities. Specifically, I can step, set breakpoints, step
>into/over, but I cannot perform data operations (Read, Evaluate/Modify, etc.).
>It doesn't seem to have the data necessary to see global and local variables.
>
>Has anyone else tried this? Any ideas on what specific data (and the required
>format) I might be able to provide to SingleStep?
>
>Thanks you.

Local variables you'll have trouble with.

Globals should be a little easier.  There are two options:

1) Figure out what symbol the Ada compiler is emitting for
the global variable you are interested in and try using that in
your debugger.  I don't know what object module format you are
using, but there's probably a tool like nm that can be used.

2) Use pragma export to give your global variables names which
are easy to type (and use in the debugger).

good luck

- Corey