Newsgroups: comp.lang.prolog
Path: cantaloupe.srv.cs.cmu.edu!das-news.harvard.edu!news2.near.net!yale!yale.edu!spool.mu.edu!umn.edu!myria!sshankar
From: sshankar@myria.cs.umn.edu (Subash Shankar)
Subject: Profiling libraries in Sicstus
Message-ID: <CvxzpM.DBr@news.cis.umn.edu>
Sender: news@news.cis.umn.edu (Usenet News Administration)
Nntp-Posting-Host: myria.cs.umn.edu
Organization: University of Minnesota, Minneapolis, CSci dept.
Date: Sun, 11 Sep 1994 01:39:56 GMT
Lines: 20



I was wondering if there is any way of profiling library routines in
Sicstus Prolog?  

Reason: I have a program which makes use of the Sicstus libraries, and
I would like to find out which parts of the program are taking the
most time, whether in the libraries or from my code.  Is there a way
to profile libraries in Sicstus?  Failing that, is there a workaround?

One thing that I tried and doesn't work is copying the library (.pl)
file to my directory and compiling it like normal (deleting the
reference to the library in my code).  In this case, the routines in
the library aren't profiled for some strange reason.

Thanks.
--
Subash Shankar
Grad Student     Computer Science     University of Minnesota 
sshankar@cs.umn.edu
