stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Liviu Nicoara (JIRA)" <>
Subject [jira] Created: (STDCXX-136) uninitialized driver emits wrong error message
Date Mon, 06 Feb 2006 22:58:57 GMT
uninitialized driver emits wrong error message

         Key: STDCXX-136
     Project: C++ Standard Library
        Type: Bug
  Components: Tests  
    Versions: 4.1.3    
 Environment: $ uname -a
Linux skynet #3 SMP PREEMPT Mon Jan 9 13:59:21 MST 2006 i686 unknown unknown GNU/Linux
$ gcc -v
Reading specs from /usr/lib/gcc-lib/i486-slackware-linux/3.3.4/specs
Configured with: ../gcc-3.3.4/configure --prefix=/usr --enable-shared --enable-threads=posix
--enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i486-slackware-linux
Thread model: posix
gcc version 3.3.4

    Reporter: Liviu Nicoara
    Priority: Trivial

The following test case:

$ cat > t.cpp << EOF

include <driver.h>

int main ()
    rw_assert (0, 0, 0, "");
    return 0;


yields the following error message:

$ ./t
/build/nicoara/stdcxx/tests/src/driver.cpp:1164: rw_assert(): test
driver already initialized

The message should indicate the driver has not been initialized. I marked it trivial because
perforce sources do not exhibit the problem. Martin suggested he problem could be in the "brittle
compatibility layer" necessary in this period of transition to enable testing in both infrastructures.


This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message