2008/7/17 Tim Jenness <[log in to unmask]>:
> Peter,
>
> Is it worth moving thread-safe ems into trunk so that we can start using it
> on a daily basis? I have no idea if David is testing it in his threaded
> smurf but I think we should be giving the thread-safe ems a bashing in
> single thread mode for a while.
I've been using thread safe EMS in my work. I've no evidence that
there are any problems with it, but on the other hand there are
certainly problems *somewhere*, which I am still struggling to track
down. The latest is that, after huge efforts, I've sort of got the
Intel Thread Checker tool running, so today's task is to see if it
gives any useful pointers to what may be wrong. BTW do you know of any
way of finding the source code line associated with a given hex
address? The Thread Checker report includes things like "[makemap]
0x13f5eb" as the place where a problem occurs. I believe everything is
compiled with "-g" so you would have thought it could give more
helpful indications of where the problem is occurred. I suppose it
could be that the problem is occurring in some external library which
is not compiled with "-g". Any suggestion on how to track down an
arbitrary address?
> I'm hoping that AST thread-safe will be default for the next release in the
> Autumn.
So am I!
David
|