stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Farid Zaripov <>
Subject [PATCH] RE: Mt tests
Date Fri, 17 Nov 2006 18:01:00 GMT
 > -----Original Message-----
 > From: Martin Sebor []
 > Sent: Friday, November 10, 2006 3:28 AM
 > To:
 > Subject: Re: Mt tests
 > I think the simplest and most reliable way might be to
 > hardcode the pathname of the executable (or just BUILDDIR)
 > into the program itself and have it use it to exec itself.

   You mean that relative path from environment variable BUILDDIR
should be hardcoded, right?

   Attached 21.string.diff is a patch to the 21.string.* files
for create multithreaded tests of basic_string class. is just example of multithreaded test (not a real test).

   First I've created new macros DEFINE_STRING_MTTEST_FUNCTIONS
and DEFINE_STRING_MTTEST_DISPATCH (and rest) to pass the number
of threads and number of loops to the test function, but finally
I've removed this because I think its a unnecessary complication.
So now number of threads and number of loops passed to the test
using global functions rw_nthreads() and rw_nloops().

   * 21.strings.h (rw_run_string_mttest): New functions to run
   multithreaded test of basic_string class
   (rw_nthreads): New function to get number of threads
   (rw_nloops): New function to get number of loops for test
   * 21.string.cpp: Ditto.
   (_rw_exename): New function to get the path to the test executable
   (_rw_run_child): New function to run a child copy of the process
   and check whether or not child test was successful
   (_rw_run_cases): Added call to the _rw_run_child
   (_rw_run_test): Added rw_info to print the number of threads,
    number of loops and timeout value
   (_rw_run_test): The number of overloads increased to 64 and
   number of installed handlers is matches to the number of overloads
   (_rw_setopts_mt): New function to set the options for
   multithreaded test


View raw message