comp.lang.ada
 help / color / mirror / Atom feed
From: parthaspanda22@gmail.com
Subject: Re: ASIS?
Date: Fri, 26 Oct 2007 07:40:29 -0700
Date: 2007-10-26T07:40:29-07:00	[thread overview]
Message-ID: <1193409629.370716.268320@z24g2000prh.googlegroups.com> (raw)
In-Reply-To: <4721ece5$0$27815$39db0f71@news.song.fi>

> You list various non-ASIS sources for the target- and
> link-map-specific information (below). Your original query was:

How? By extending the ASIS spec to include map file information,
isnt the map file made redundant? Of course, it will
require multiple tools in the chain to write to
a common ASIS database.

>
>  > If one were to need an API to fulfill all requirements by
>  > a Debugger, Source Browser and a Syntax-aware editor from
>  > the IDE, then would ASIS be it?
>
> It was the point "all requirements" to which I objected, but I must
> have misunderstood or not noticed your phrase "... from the IDE",
> which I now understand means "... apart from the information that
> can be had from other sources". But there are some executable
> program formats that include most of the ASIS-like information (for
> C code, at least), so for such executable formats a debugger would
> need no additional information from the IDE.

It would be difficult to debug Generics or variant record types
unless there were a HLL interface. I expect ASIS to atleast
be able to address all Ada-specific syntactic sugar.
(There is a link to JSIS, but alas, it leads to
a useless site.)

>
> Anyway, your question and Ludovic's answer are sensible if one
> assumes that the "other sources" are some limited executable format
> such as ELF without DWARF.

Yes, a debugger must still need access to a working executable
for instrumentation. Machine-level debugging hasnt been
pursued that extensively by processors, so executable
instrumentation(i.e. SW debugging) is generally the norm.

>
> Yes, or the debugging info in the executable file.
>
> > 2) stack-frame
>
> >     A lot of the information about stack are constants(e.g. the bias,
> >     the frame pointer register, the stack pointer register,
> >     the ABI) and these are hard-wired into the debugger.
>
> Depends on the target. Some ABIs are very flexible and let the
> compiler do what it likes.

The scope of my research precludes going on a path where
the ABI is "flexible" but there are many examples of
your point, so I cant agree more.





  reply	other threads:[~2007-10-26 14:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26  9:47 ASIS? parthaspanda22
2007-10-26 10:09 ` ASIS? Ludovic Brenta
2007-10-26 11:58   ` ASIS? parthaspanda22
2007-10-26 12:10     ` ASIS? parthaspanda22
2007-10-26 12:29   ` ASIS? Niklas Holsti
2007-10-26 13:00     ` ASIS? parthaspanda22
2007-10-26 13:43       ` ASIS? Niklas Holsti
2007-10-26 14:40         ` parthaspanda22 [this message]
2007-10-27 12:21           ` ASIS? Niklas Holsti
2007-10-27  0:15     ` ASIS? Randy Brukardt
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox