[muscle] Re: Server problem with Insure

Julien,

Thanks for the report.  When do these error messages occur?  (i.e. do they=
=20
errors occur when muscled starts, or whenever a client connects, or only wh=
en=20
the first client connects, or?)

Also, can you try setting MEMORY_TRACKING_SUPPORTED to "no" in the Makefile=
=20
and then re-compiling muscled and re-running the test?  (that should remove=
=20
the -DMUSCLE_ENABLE_MEMORY_TRACKING define from the build arguments, so tha=
t=20
muscled doesn't overload the new and delete operators to track its memory=20
usage.... in my experience having that enabled sometimes confuses debugging=
=20
tools)

Thanks,
Jeremy

On Wednesday 27 October 2004 08:42, Julien Torr=E8s wrote:
> Hello.
>
> I tried to instrument Muscle with Insure 7.0 from Parasoft. Insure=3D20
> reports several errors. Here is the report. I suppressed some errors=3D20
> that do not seems very important. But some remains. Insure reports the=3D=
20
> error type, the corresponding C++ file and line, and the successive=3D20
> calls from the stack. I hope this could help.
>
> =3D2D-=3D20
> Julien Torr=3DE8s

Other related posts: