[m-rev.] for review: --debug-threads runtime option

[Fergus Henderson]

On 03-Mar-2003, Peter Ross <pro at missioncriticalit.com> wrote:
> On Tue, Mar 04, 2003 at 12:38:26AM +1100, Fergus Henderson wrote:
> > On 03-Mar-2003, Peter Ross <pro at missioncriticalit.com> wrote:
> > > Allow one to turn thread debugging on at runtime.
> > > However only modules which are compiled with MR_DEBUG_THREADS will
> > > have debugging messages output.
> > 
> > Well, I'm not sure how useful this is.  But at any rate that change looks
> > mostly harmless.  I do have some comments about the documentation,
> > though.
>
> It is very useful when one is trying to debug deadlock problems
> (particularly prevalent because it is rare that foreign_procs are marked
> thread_safe) without having to do a complete recompile (including
> runtime and standard library).

I can see how that part of your change is useful -- the part which
defines the debugging routines unconditionally, hence allowing
different modules to be compiled with different settings of
MR_DEBUG_THREADS.

But the run-time option seems less useful.  After all, if you've just
recompiled all your modules with `-DMR_DEBUG_THREADS', you probably want
to enable thread debugging.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
The University of Melbourne         |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------