Re: [OMPI devel] snprintf vs. sprintf

2008-10-29 Thread Matthias Jurenz
Yes, I'll do it tomorrow... Before that, I whould like to check the next MTT results to see whether the trunk is ok or not ;-) On Mi, 2008-10-29 at 12:25 -0400, Jeff Squyres wrote: > BTW, don't forget to CMR all your VT changes to v1.3. > > > On Oct 29, 2008, at 12:23 PM, Jeff Squyres wrote: >

Re: [OMPI devel] snprintf vs. sprintf

2008-10-29 Thread Jeff Squyres
BTW, don't forget to CMR all your VT changes to v1.3. On Oct 29, 2008, at 12:23 PM, Jeff Squyres wrote: Done (for my upcoming commit with this stuff). Thanks! On Oct 29, 2008, at 12:05 PM, Matthias Jurenz wrote: On Mi, 2008-10-29 at 08:43 -0400, Jeff Squyres wrote: On Oct 29, 2008, at 8:

Re: [OMPI devel] snprintf vs. sprintf

2008-10-29 Thread Jeff Squyres
Done (for my upcoming commit with this stuff). Thanks! On Oct 29, 2008, at 12:05 PM, Matthias Jurenz wrote: On Mi, 2008-10-29 at 08:43 -0400, Jeff Squyres wrote: On Oct 29, 2008, at 8:14 AM, Matthias Jurenz wrote: > The problem should be fixed in the trunk. VampirTrace also comes now > w

Re: [OMPI devel] snprintf vs. sprintf

2008-10-29 Thread Matthias Jurenz
On Mi, 2008-10-29 at 08:43 -0400, Jeff Squyres wrote: > On Oct 29, 2008, at 8:14 AM, Matthias Jurenz wrote: > > > The problem should be fixed in the trunk. VampirTrace also comes now > > with an own > > implementation of 'snprintf'. More precisely, the corresponding > > sources are based on >

Re: [OMPI devel] snprintf vs. sprintf

2008-10-29 Thread Jeff Squyres
CMR, please. You can say I reviewed it. Thanks! On Oct 29, 2008, at 9:21 AM, Matthias Jurenz wrote: On Mi, 2008-10-29 at 08:43 -0400, Jeff Squyres wrote: On Oct 29, 2008, at 8:14 AM, Matthias Jurenz wrote: > The problem should be fixed in the trunk. VampirTrace also comes now > with an

Re: [OMPI devel] snprintf vs. sprintf

2008-10-29 Thread Matthias Jurenz
On Mi, 2008-10-29 at 08:43 -0400, Jeff Squyres wrote: > On Oct 29, 2008, at 8:14 AM, Matthias Jurenz wrote: > > > The problem should be fixed in the trunk. VampirTrace also comes now > > with an own > > implementation of 'snprintf'. More precisely, the corresponding > > sources are based on >

Re: [OMPI devel] snprintf vs. sprintf

2008-10-29 Thread Jeff Squyres
On Oct 29, 2008, at 8:14 AM, Matthias Jurenz wrote: The problem should be fixed in the trunk. VampirTrace also comes now with an own implementation of 'snprintf'. More precisely, the corresponding sources are based on 'opal/util/printf.' and located in 'ompi/contrib/vt/vt/util/ util.c'. Conc

Re: [OMPI devel] snprintf vs. sprintf

2008-10-29 Thread Matthias Jurenz
The problem should be fixed in the trunk. VampirTrace also comes now with an own implementation of 'snprintf'. More precisely, the corresponding sources are based on 'opal/util/printf.' and located in 'ompi/contrib/vt/vt/util/util.c'. Concerning this matter, I want to know, whether there is a copy

Re: [OMPI devel] snprintf vs. sprintf

2008-10-27 Thread George Bosilca
Brad, We have our version of snprintf, just in case the installed standard library doesn't support it. This function called opal_snprintf will be aliased to snprintf (./opal/include/opal_config_bottom.h:410). As you are supposed to always include opal_config.h as first header in your file