[m-rev.] ssdb v1.0 fixed

[Julien Fischer]

On Wed, 5 Dec 2007, Peter Wang wrote:

> On 2007-12-05, Julien Fischer <juliensf at csse.unimelb.edu.au> wrote:
>>>        I'm not sure where the ssdb transform should go. I assume as early
>>> as
>>> 	possible.
>>
>>  I think the opposite is probably true.
>
> One problem with doing that is that putting breakpoints on the original
> procedures won't work reliably because earlier transformations may have
> e.g. specialised that procedure and changed the call sites.  Which
> practically means disabling all transformations that might affect the
> user's view of the program if ssdb is enabled.

Which is what mdb does.  I think trying to preserve the user's
view of the program in the presence of program transformations is
a fairly tall order.

>>> Index: profiler/Mmakefile
>>> ===================================================================
>>> RCS file: /home/mercury1/repository/mercury/profiler/Mmakefile,v
>>> retrieving revision 1.30
>>> diff -u -r1.30 Mmakefile
>>> --- profiler/Mmakefile	4 Dec 2007 13:51:00 -0000	1.30
>>> +++ profiler/Mmakefile	5 Dec 2007 02:03:08 -0000
>>> @@ -17,6 +17,8 @@
>>> MAIN_TARGET=all
>>> MERCURY_MAIN_MODULES=mercury_profile
>>>
>>> +VPATH = $(LIBRARY_DIR) $(SSDB_DIR)
>>> +
>>> #-----------------------------------------------------------------------------#
>>
>>  Is there a reason a similar change is not necessary in the deep_profiler
>>  directory?
>
> The bootcheck we tried probably didn't build the deep profiler so it
> wasn't noticed.

I thought I fixed that a few weeks ago.

Julien.
--------------------------------------------------------------------------
mercury-reviews mailing list
Post messages to:       mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions:          mercury-reviews-request at csse.unimelb.edu.au
--------------------------------------------------------------------------