f



[ace-users] Tests failed : ACE 5.5.2 - AIX 5.3 - GCC 4.1.1

Hi,
My first mail before my message in the group failed (my subscription was not 
activated).

The PRF below describes my problems. I can compile and link but several
ACE's tests fail.  I only use ACE library and only compile it by cd'ing in
the ace directory before running make. I already made some fixes described
below to compile and to link the library. I'm not abble to interpret the
faild tests to identify the problem source or area.

I didn't find the scoreboard before my mail. I see that several tests fails 
for
all compilations on AIX. I try to reassure myself by looking these results, 
it's
not only for my configuration. But it's a daily build with last development 
version.
For the 5.5.2 stable version they should probably not fail ?

Regards,
PO Houot.

ACE VERSION: 5.5.2

    HOST MACHINE and OPERATING SYSTEM:
bash-3.00$ uname -a
AIX localhost 3 5 0040983B4C00 unknown unknown AIX
bash-3.00$ oslevel -r
5300-05

    TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
Same as host

    COMPILER NAME AND VERSION (AND PATCHLEVEL):
bash-3.00$ g++ -v
Using built-in specs.
Target: powerpc-ibm-aix5.3.0.0
Configured with: ../gcc-4.1.1/configure --disable-nls
Thread model: aix
gcc version 4.1.1

This compiler is installed from packages provided by UCLA AIX Software
library

    THE $ACE_ROOT/ace/config.h FILE :
bash-3.00$ more $ACE_ROOT/ace/config.h
#include "ace/config-aix-5.x.h"

    THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE :
bash-3.00$ more $ACE_ROOT/include/makeinclude/platform_macros.GNU
include $(ACE_ROOT)/include/makeinclude/platform_aix_g++.GNU

    CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/default.features :
No such file

    AREA/CLASS/EXAMPLE AFFECTED:

    DOES THE PROBLEM AFFECT:
        COMPILATION?
First problem was :
Based_Pointer_Repository.cpp:118: error: duplicate explicit instantiation of
'ACE_Singleton<ACE_Based_Pointer_Repository, ACE_RW_Thread_Mutex>*
ACE_Singleton<ACE_Based_Pointer_Repository,
ACE_RW_Thread_Mutex>::singleton_'
Fixed with message
http://groups.google.fr/group/comp.soft-sys.ace/browse_thread/thread/aee9d3d172a59172/ea326c9c1e1fe3e0?lnk=gst&q=aix+gcc+4&rnum=3#ea326c9c1e1fe3e0
from Steve Huston.

Now many warnings about visibility
(options -fvisibility=hidden -fvisibility-inlines-hidden)
ace/String_Base.cpp:118: warning: visibility attribute not supported in this
configuration; ignored
This should probably no matter. I don't know

        LINKING?
First problem was :
ar cruv libACE.a.5.5.2 shr.o
BFD: shr.o: Unrecognized storage class 0 for *ABS* symbol
`/home/public/build/build-gcc-4.1.1/ACE_5.5/ACE_wrappers/ace/OS_NS_Thread.inl'
// Repeated many times
Fixed with this message
http://groups.google.fr/group/comp.soft-sys.ace/browse_thread/thread/c78c2c061a2f5d43/9b59f7d3cf34175f?lnk=st&q=&rnum=2&hl=fr#9b59f7d3cf34175f
from Randy Hammon

Now I only have several warnings (French version, means duplicated symbols)
ld : 0711-224 AVERTISSEMENT : Symbole thread_creds_t en double.
ld : 0711-224 AVERTISSEMENT : Symbole ras_arg_t en double.
ld : 0711-224 AVERTISSEMENT : Symbole fc_softc en double.
ld : 0711-224 AVERTISSEMENT : Symbole .global destructors keyed to
thread_creds_ten double.
ld : 0711-224 AVERTISSEMENT : Symbole .global constructors keyed to
thread_creds_ten double.
ld : 0711-224 AVERTISSEMENT : Symbole global constructors keyed to
thread_creds_ten double.
ld : 0711-224 AVERTISSEMENT : Symbole global destructors keyed to
thread_creds_ten double.
Does it affect my library ?

            On Unix systems, did you run make realclean first? yes

        EXECUTION?
Several tests fail, this is the list and an extract of the log files

auto_run_tests_finished: test/Based_Pointer_Test Time:1s Result:1
Error: (log/Based_Pointer_Test.log): MMAP pool mapping not present
Error: (log/Based_Pointer_Test.log): Persistent MMAP Memory Pool not mapped
Error: (log/Based_Pointer_Test.log): New base address not mapped after MMAP
remap

auto_run_tests: tests/Buffer_Stream_Test
ACE_ASSERT: file
/home/public/build/build-gcc-4.1.1/ACE_5.5/ACE_wrappers/ace/Module.cpp, line
256 assertion failed for 'task->thr_count () == 0'.Aborting...

auto_run_tests: tests/Bug_2368_Regression_Test
auto_run_tests_finished: test/Bug_2368_Regression_Test Time:1s Result:0
Error: (log/Bug_2368_Regression_Test.log): Handle close hasn't been called
for A
Error: (log/Bug_2368_Regression_Test.log): Handle close hasn't been called
for B

auto_run_tests: tests/Bug_2540_Regression_Test
ERROR: Bug_2540_Regression_Test timedout
Error: Bug_2540_Regression_Test FAILED (time out)
auto_run_tests_finished: test/Bug_2540_Regression_Test Time:401s Result:-1

auto_run_tests: tests/Conn_Test
ERROR: <Conn_Test> exited with coredump from signal 4 : ILL
auto_run_tests_finished: test/Conn_Test Time:3s Result:0
Error: Conn_Test dumped core
Error (log/Conn_Test.log): no line with 'Ending'
======= Begin Log File
Aug 23 16:48:30.812 2006@LM_DEBUG@(48868|1) Starting Conn_Test test at Wed
Aug 23 2006 16:48:30.812963
Aug 23 16:48:32.643 2006@LM_DEBUG@(48868|1) starting server at port 36413
Aug 23 16:48:32.688 2006@LM_DEBUG@(48868|258) **** starting timed-blocking
connect
Aug 23 16:48:32.689 2006@LM_DEBUG@(48868|258) opening Svc_Handler 20091a68
with handle 7
Aug 23 16:48:32.690 2006@LM_DEBUG@(48868|258) **** starting blocking connect
Aug 23 16:48:32.690 2006@LM_DEBUG@(48868|258) opening Svc_Handler 20091a68
with handle 7
Aug 23 16:48:32.691 2006@LM_DEBUG@(48868|258) **** starting cached blocking
connect
Aug 23 16:48:32.691 2006@LM_DEBUG@(53750|1) opening Svc_Handler 2006a4f8
with handle 7
Aug 23 16:48:32.693 2006@LM_DEBUG@(54468|1) opening Svc_Handler 2006a4f8
with handle 7
Aug 23 16:48:32.695 2006@LM_DEBUG@(53750|1) client localhost connected from
36414
Aug 23 16:48:32.696 2006@LM_DEBUG@(53750|1) reached end of input, connection
closed by client
Aug 23 16:48:32.696 2006@LM_DEBUG@(54468|1) client localhost connected from
36415
Aug 23 16:48:32.697 2006@LM_DEBUG@(54468|1) reached end of input, connection
closed by client
======= End Log File

auto_run_tests: tests/Future_Set_Test
ERROR: <Future_Set_Test> exited with coredump from signal 4 : ILL
auto_run_tests_finished: test/Future_Set_Test Time:2s Result:0
Error: Future_Set_Test dumped core
Error (log/Future_Set_Test.log): no line with 'Ending'
======= Begin Log File
Aug 23 16:48:44.672 2006@LM_DEBUG@(48890|1) Starting Future_Set_Test test at
Wed Aug 23 2006 16:48:44.672866
Aug 23 16:48:44.673 2006@LM_DEBUG@(1) Prime_Scheduler andres created
..... Too long

auto_run_tests: tests/Future_Test
ERROR: <Future_Test> exited with coredump from signal 4 : ILL
auto_run_tests_finished: test/Future_Test Time:1s Result:0
Error: Future_Test dumped core
Error (log/Future_Test.log): no line with 'Ending'
======= Begin Log File
Aug 23 16:48:46.870 2006@LM_DEBUG@(56818|1) Starting Future_Test test at Wed
Aug 23 2006 16:48:46.870494
..... Too long

auto_run_tests: tests/MT_Reference_Counted_Event_Handler_Test
ACE_ASSERT: file MT_Reference_Counted_Event_Handler_Test.cpp, line 832
assertion failed for 'result == 0'.Aborting...

auto_run_tests: tests/MT_Reference_Counted_Notify_Test
ERROR: <MT_Reference_Counted_Notify_Test> exited with coredump from signal 4
: ILL
auto_run_tests_finished: test/MT_Reference_Counted_Notify_Test Time:3s
Result:0
Error: MT_Reference_Counted_Notify_Test dumped core
Error (log/MT_Reference_Counted_Notify_Test.log): no line with 'Ending'
======= Begin Log File
Aug 23 16:50:23.495 2006@LM_DEBUG@(56438|1) Starting
MT_Reference_Counted_Notify_Test test at Wed Aug 23 2006 16:50:23.496013
Aug 23 16:50:23.496 2006@LM_DEBUG@

Testing Select Reactor....

Aug 23 16:50:23.496 2006@LM_DEBUG@

Testing empty notifies...

Aug 23 16:50:23.512 2006@LM_DEBUG@Event Loop iteration 1....
Aug 23 16:50:24.013 2006@LM_DEBUG@Event Loop iteration 2....
Aug 23 16:50:24.513 2006@LM_DEBUG@Event Loop iteration 3....
Aug 23 16:50:25.013 2006@LM_DEBUG@Event Loop iteration 4....
Aug 23 16:50:25.513 2006@LM_DEBUG@Event Loop iteration 5....
======= End Log File

auto_run_tests: tests/Message_Block_Test
ERROR: <Message_Block_Test> exited with coredump from signal 4 : ILL
auto_run_tests_finished: test/Message_Block_Test Time:1s Result:0
Error: Message_Block_Test dumped core
Error (log/Message_Block_Test.log): no line with 'Ending'
======= Begin Log File
Aug 23 16:52:00.745 2006@LM_DEBUG@(55460|1) Starting Message_Block_Test test
at Wed Aug 23 2006 16:52:0
0.745814
Aug 23 16:52:00.746 2006@LM_DEBUG@(1) threads = 4
Aug 23 16:52:00.746 2006@LM_DEBUG@(1) Start Message_Block_Test using Default
allocation strategy
Aug 23 16:52:00.748 2006@LM_DEBUG@(515) starting svc() method
Aug 23 16:52:00.748 2006@LM_DEBUG@(258) starting svc() method
Aug 23 16:52:00.748 2006@LM_DEBUG@
(1) sending shutdown message
Aug 23 16:52:00.748 2006@LM_DEBUG@
(1) end producer
Aug 23 16:52:00.748 2006@LM_DEBUG@(1) waiting for worker tasks to finish...
Aug 23 16:52:00.748 2006@LM_DEBUG@(1) destroying worker tasks
======= End Log File

auto_run_tests: tests/Message_Queue_Test
auto_run_tests_finished: test/Message_Queue_Test Time:1s Result:0
Error: (log/Message_Queue_Test.log): enqueue: Invalid argument
Error: (log/Message_Queue_Test.log): dequeue_head: Invalid argument

auto_run_tests: tests/Message_Queue_././Message_Queue_Test_Ex
ERROR: <Message_Queue_Test_Ex> exited with coredump from signal 11 : SEGV
auto_run_tests_finished: test/Message_Queue_Test_Ex Time:1s Result:0
Error: Message_Queue_Test_Ex dumped core
Error (log/Message_Queue_Test_Ex.log): no line with 'Ending'
======= Begin Log File
Aug 23 16:52:03.811 2006@LM_DEBUG@(55466|1) Starting Message_Queue_Test_Ex
test at Wed Aug 23 2006 16:52:03.811960
Aug 23 16:52:03.814 2006@LM_DEBUG@Timed dequeue test: OK
Aug 23 16:52:03.858 2006@LM_INFO@ACE_Message_Queue_Ex<ACE_NULL_SYNCH>,
single thread: 10000 messages took 33 msec (0.003300 msec/message)
Aug 23 16:52:03.877 2006@LM_INFO@ACE_Message_Queue_Ex<ACE_SYNCH>: 10000
messages took 3152383431 msec (315238.343100 msec/message)
======= End Log File

auto_run_tests: tests/Process_Manual_Event_Test
ERROR: Process_Manual_Event_Test timedout
Error: Process_Manual_Event_Test FAILED (time out)
auto_run_tests_finished: test/Process_Manual_Event_Test Time:400s Result:-1
Error (log/Process_Manual_Event_Test.log): no line with 'Ending'
======= Begin Log File
Aug 23 16:52:44.365 2006@LM_DEBUG@(53186|1) Starting
Process_Manual_Event_Test test at Wed Aug 23 2006 16:52:44.365994
Aug 23 16:52:44.382 2006@LM_DEBUG@Parent spawned child process with pid =
57384.
Aug 23 16:52:44.383 2006@LM_DEBUG@(53186) Begin ping-pong
Aug 23 16:52:44.384 2006@LM_DEBUG@(53186) Ping
======= End Log File
Error (Process_Manual_Event_Test-child.log): no line with 'Ending'
Error (Process_Manual_Event_Test-child.log): Number of 'Starting' does not
match number of 'Ending' (1!= 0)
======= Begin Sublog File Process_Manual_Event_Test-child.log
Aug 23 16:52:44.384 2006@LM_DEBUG@(57384|1) Starting
Process_Manual_Event_Test-child test at Wed Aug 23
 2006 16:52:44.384052
Aug 23 16:52:44.384 2006@LM_DEBUG@(57384) Begin ping-pong
Aug 23 16:52:44.384 2006@LM_DEBUG@(57384) Pong
======= End Sublog File

auto_run_tests: tests/Recursive_Condition_Test
auto_run_tests_finished: test/Recursive_Condition_Test Time:20s Result:0
Error: (log/Recursive_Condition_Test.log): (258) waiter found protected_int
1
Error: (log/Recursive_Condition_Test.log): (515) waiter found protected_int
1
Error: (log/Recursive_Condition_Test.log): (772) waiter found protected_int
3
Error: (log/Recursive_Condition_Test.log): (1029) waiter found protected_int
3
Error: (log/Recursive_Condition_Test.log): (1286) waiter found protected_int
3
Error: (log/Recursive_Condition_Test.log): (1543) waiter found protected_int
3

auto_run_tests: tests/Signal_Test
auto_run_tests_finished: test/Signal_Test Time:3s Result:0
Error (Signal_Test-child.log): Number of 'Starting' does not match number of
'Ending' (3 != 2)
======= Begin Sublog File Signal_Test-child.log
Aug 23 17:01:36.923 2006@LM_DEBUG@(59354|1) Starting Signal_Test-child test
at Wed Aug 23 2006 17:01:36.923201
Aug 23 17:01:36.923 2006@LM_DEBUG@(59354|1) **** test 1: handle signals
synchronously in separate thread
Aug 23 17:01:36.923 2006@LM_DEBUG@(59354|1) spawning worker thread
Aug 23 17:01:36.924 2006@LM_DEBUG@(59354|1) spawning signal handler thread
Aug 23 17:01:36.924 2006@LM_DEBUG@(59354|1) Ending Signal_Test-child test at
Wed Aug 23 2006 17:01:36.924462

Aug 23 17:01:36.933 2006@LM_DEBUG@(19328|1) Starting Signal_Test-child test
at Wed Aug 23 2006 17:01:36.933329
Aug 23 17:01:36.933 2006@LM_DEBUG@(19328|1) **** test 2: handle signals
synchronously in this thread
Aug 23 17:01:36.933 2006@LM_DEBUG@(19328|1) spawning worker thread
Aug 23 17:01:36.940 2006@LM_DEBUG@(19328|258) sleeping for 2 seconds
Aug 23 17:01:38.940 2006@LM_DEBUG@(19328|258) sending SIGHUP to parent
process 59106
Aug 23 17:01:38.940 2006@LM_DEBUG@(19328|258) sleeping for 2 seconds
Aug 23 17:01:38.952 2006@LM_DEBUG@(19328|1) synchronous signal handler done
Aug 23 17:01:38.952 2006@LM_DEBUG@(19328|1) Ending Signal_Test-child test at
Wed Aug 23 2006 17:01:38.952947

Aug 23 17:01:38.961 2006@LM_DEBUG@(59356|1) Starting Signal_Test-child test
at Wed Aug 23 2006 17:01:38.961491
Aug 23 17:01:38.961 2006@LM_DEBUG@(59356|1) **** test 3: handle signals
asynchronously in this thread
Aug 23 17:01:38.961 2006@LM_DEBUG@(59356|1) sleeping for 2 seconds
======= End Sublog File

auto_run_tests: tests/SOCK_Connector_Test
auto_run_tests_finished: test/SOCK_Connector_Test Time:1s Result:0
Warning: (log/SOCK_Connector_Test.log): Immediate success/fail; test not
completed
======= Begin Log File
Aug 23 17:01:39.936 2006@LM_DEBUG@(59108|1) Starting SOCK_Connector_Test
test at Wed Aug 23 2006 17:01:39.936512
Aug 23 17:01:39.942 2006@LM_DEBUG@Testing to host "localhost"
Aug 23 17:01:39.944 2006@LM_DEBUG@Proper fail: Connection refused
Aug 23 17:01:39.944 2006@LM_DEBUG@Testing to host "localhost", port 7
Aug 23 17:01:39.944 2006@LM_WARNING@Immediate success/fail; test not
completed
Aug 23 17:01:39.944 2006@LM_DEBUG@(59108|1) Ending SOCK_Connector_Test test
at Wed Aug 23 2006 17:01:39.944501

auto_run_tests: tests/Thread_Pool_Reactor_Resume_Test
terminate called after throwing an instance of 'std::ios_base::failure'
  what():  basic_ios::clear
auto_run_tests_finished: test/Thread_Pool_Reactor_Resume_Test Time:4s
Result:0
Error: Thread_Pool_Reactor_Resume_Test dumped core

auto_run_tests: tests/Thread_Pool_Reactor_Test
terminate called after throwing an instance of 'std::ios_base::failure'
  what():  basic_ios::clear
auto_run_tests_finished: test/Thread_Pool_Reactor_Test Time:4s Result:0
Error: Thread_Pool_Reactor_Test dumped core

auto_run_tests: tests/Recursive_Condition_Bug_Test
ERROR: <Recursive_Condition_Bug_Test> exited with coredump from signal 4 :
ILL
auto_run_tests_finished: test/Recursive_Condition_Bug_Test Time:1s Result:0
Error: Recursive_Condition_Bug_Test dumped core


        OTHER (please specify)?

    SYNOPSIS:

    DESCRIPTION:

    REPEAT BY:
Each time the tests are executed with run_test.pl

    SAMPLE FIX/WORKAROUND:
None
Hi,
The PRF below describes my problems. I can compile and link but several
ACE's tests fail.  I only use ACE library and only compile it by cd'ing in
the ace directory before running make. I already made some fixes described
below to compile and to link the library. I'm not abble to interpret the
faild tests to identify the problem source or area.

Regards,
PO Houot.

ACE VERSION: 5.5.2

    HOST MACHINE and OPERATING SYSTEM:
bash-3.00$ uname -a
AIX localhost 3 5 0040983B4C00 unknown unknown AIX
bash-3.00$ oslevel -r
5300-05

    TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
Same as host

    COMPILER NAME AND VERSION (AND PATCHLEVEL):
bash-3.00$ g++ -v
Using built-in specs.
Target: powerpc-ibm-aix5.3.0.0
Configured with: ../gcc-4.1.1/configure --disable-nls
Thread model: aix
gcc version 4.1.1

This compiler is installed from packages provided by UCLA AIX Software
library

    THE $ACE_ROOT/ace/config.h FILE :
bash-3.00$ more $ACE_ROOT/ace/config.h
#include "ace/config-aix-5.x.h"

    THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE :
bash-3.00$ more $ACE_ROOT/include/makeinclude/platform_macros.GNU
include $(ACE_ROOT)/include/makeinclude/platform_aix_g++.GNU

    CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/default.features :
No such file

    AREA/CLASS/EXAMPLE AFFECTED:

    DOES THE PROBLEM AFFECT:
        COMPILATION?
First problem was :
Based_Pointer_Repository.cpp:118: error: duplicate explicit instantiation of
'ACE_Singleton<ACE_Based_Pointer_Repository, ACE_RW_Thread_Mutex>*
ACE_Singleton<ACE_Based_Pointer_Repository,
ACE_RW_Thread_Mutex>::singleton_'
Fixed with message
http://groups.google.fr/group/comp.soft-sys.ace/browse_thread/thread/aee9d3d172a59172/ea326c9c1e1fe3e0?lnk=gst&q=aix+gcc+4&rnum=3#ea326c9c1e1fe3e0
from Steve Huston.

Now many warnings about visibility
(options -fvisibility=hidden -fvisibility-inlines-hidden)
ace/String_Base.cpp:118: warning: visibility attribute not supported in this
configuration; ignored
This should probably no matter. I don't know

        LINKING?
First problem was :
ar cruv libACE.a.5.5.2 shr.o
BFD: shr.o: Unrecognized storage class 0 for *ABS* symbol
`/home/public/build/build-gcc-4.1.1/ACE_5.5/ACE_wrappers/ace/OS_NS_Thread.inl'
// Repeated many times
Fixed with this message
http://groups.google.fr/group/comp.soft-sys.ace/browse_thread/thread/c78c2c061a2f5d43/9b59f7d3cf34175f?lnk=st&q=&rnum=2&hl=fr#9b59f7d3cf34175f
from Randy Hammon

Now I only have several warnings (French version, means duplicated symbols)
ld : 0711-224 AVERTISSEMENT : Symbole thread_creds_t en double.
ld : 0711-224 AVERTISSEMENT : Symbole ras_arg_t en double.
ld : 0711-224 AVERTISSEMENT : Symbole fc_softc en double.
ld : 0711-224 AVERTISSEMENT : Symbole .global destructors keyed to
thread_creds_ten double.
ld : 0711-224 AVERTISSEMENT : Symbole .global constructors keyed to
thread_creds_ten double.
ld : 0711-224 AVERTISSEMENT : Symbole global constructors keyed to
thread_creds_ten double.
ld : 0711-224 AVERTISSEMENT : Symbole global destructors keyed to
thread_creds_ten double.
Does it affect my library ?

            On Unix systems, did you run make realclean first? yes

        EXECUTION?
Several tests fail, this is the list and an extract of the log files

auto_run_tests_finished: test/Based_Pointer_Test Time:1s Result:1
Error: (log/Based_Pointer_Test.log): MMAP pool mapping not present
Error: (log/Based_Pointer_Test.log): Persistent MMAP Memory Pool not mapped
Error: (log/Based_Pointer_Test.log): New base address not mapped after MMAP
remap

auto_run_tests: tests/Buffer_Stream_Test
ACE_ASSERT: file
/home/public/build/build-gcc-4.1.1/ACE_5.5/ACE_wrappers/ace/Module.cpp, line
256 assertion failed for 'task->thr_count () == 0'.Aborting...

auto_run_tests: tests/Bug_2368_Regression_Test
auto_run_tests_finished: test/Bug_2368_Regression_Test Time:1s Result:0
Error: (log/Bug_2368_Regression_Test.log): Handle close hasn't been called
for A
Error: (log/Bug_2368_Regression_Test.log): Handle close hasn't been called
for B

auto_run_tests: tests/Bug_2540_Regression_Test
ERROR: Bug_2540_Regression_Test timedout
Error: Bug_2540_Regression_Test FAILED (time out)
auto_run_tests_finished: test/Bug_2540_Regression_Test Time:401s Result:-1

auto_run_tests: tests/Conn_Test
ERROR: <Conn_Test> exited with coredump from signal 4 : ILL
auto_run_tests_finished: test/Conn_Test Time:3s Result:0
Error: Conn_Test dumped core
Error (log/Conn_Test.log): no line with 'Ending'
======= Begin Log File
Aug 23 16:48:30.812 2006@LM_DEBUG@(48868|1) Starting Conn_Test test at Wed
Aug 23 2006 16:48:30.812963
Aug 23 16:48:32.643 2006@LM_DEBUG@(48868|1) starting server at port 36413
Aug 23 16:48:32.688 2006@LM_DEBUG@(48868|258) **** starting timed-blocking
connect
Aug 23 16:48:32.689 2006@LM_DEBUG@(48868|258) opening Svc_Handler 20091a68
with handle 7
Aug 23 16:48:32.690 2006@LM_DEBUG@(48868|258) **** starting blocking connect
Aug 23 16:48:32.690 2006@LM_DEBUG@(48868|258) opening Svc_Handler 20091a68
with handle 7
Aug 23 16:48:32.691 2006@LM_DEBUG@(48868|258) **** starting cached blocking
connect
Aug 23 16:48:32.691 2006@LM_DEBUG@(53750|1) opening Svc_Handler 2006a4f8
with handle 7
Aug 23 16:48:32.693 2006@LM_DEBUG@(54468|1) opening Svc_Handler 2006a4f8
with handle 7
Aug 23 16:48:32.695 2006@LM_DEBUG@(53750|1) client localhost connected from
36414
Aug 23 16:48:32.696 2006@LM_DEBUG@(53750|1) reached end of input, connection
closed by client
Aug 23 16:48:32.696 2006@LM_DEBUG@(54468|1) client localhost connected from
36415
Aug 23 16:48:32.697 2006@LM_DEBUG@(54468|1) reached end of input, connection
closed by client
======= End Log File

auto_run_tests: tests/Future_Set_Test
ERROR: <Future_Set_Test> exited with coredump from signal 4 : ILL
auto_run_tests_finished: test/Future_Set_Test Time:2s Result:0
Error: Future_Set_Test dumped core
Error (log/Future_Set_Test.log): no line with 'Ending'
======= Begin Log File
Aug 23 16:48:44.672 2006@LM_DEBUG@(48890|1) Starting Future_Set_Test test at
Wed Aug 23 2006 16:48:44.672866
Aug 23 16:48:44.673 2006@LM_DEBUG@(1) Prime_Scheduler andres created
..... Too long

auto_run_tests: tests/Future_Test
ERROR: <Future_Test> exited with coredump from signal 4 : ILL
auto_run_tests_finished: test/Future_Test Time:1s Result:0
Error: Future_Test dumped core
Error (log/Future_Test.log): no line with 'Ending'
======= Begin Log File
Aug 23 16:48:46.870 2006@LM_DEBUG@(56818|1) Starting Future_Test test at Wed
Aug 23 2006 16:48:46.870494
..... Too long

auto_run_tests: tests/MT_Reference_Counted_Event_Handler_Test
ACE_ASSERT: file MT_Reference_Counted_Event_Handler_Test.cpp, line 832
assertion failed for 'result == 0'.Aborting...

auto_run_tests: tests/MT_Reference_Counted_Notify_Test
ERROR: <MT_Reference_Counted_Notify_Test> exited with coredump from signal 4
: ILL
auto_run_tests_finished: test/MT_Reference_Counted_Notify_Test Time:3s
Result:0
Error: MT_Reference_Counted_Notify_Test dumped core
Error (log/MT_Reference_Counted_Notify_Test.log): no line with 'Ending'
======= Begin Log File
Aug 23 16:50:23.495 2006@LM_DEBUG@(56438|1) Starting
MT_Reference_Counted_Notify_Test test at Wed Aug 23 2006 16:50:23.496013
Aug 23 16:50:23.496 2006@LM_DEBUG@

Testing Select Reactor....

Aug 23 16:50:23.496 2006@LM_DEBUG@

Testing empty notifies...

Aug 23 16:50:23.512 2006@LM_DEBUG@Event Loop iteration 1....
Aug 23 16:50:24.013 2006@LM_DEBUG@Event Loop iteration 2....
Aug 23 16:50:24.513 2006@LM_DEBUG@Event Loop iteration 3....
Aug 23 16:50:25.013 2006@LM_DEBUG@Event Loop iteration 4....
Aug 23 16:50:25.513 2006@LM_DEBUG@Event Loop iteration 5....
======= End Log File

auto_run_tests: tests/Message_Block_Test
ERROR: <Message_Block_Test> exited with coredump from signal 4 : ILL
auto_run_tests_finished: test/Message_Block_Test Time:1s Result:0
Error: Message_Block_Test dumped core
Error (log/Message_Block_Test.log): no line with 'Ending'
======= Begin Log File
Aug 23 16:52:00.745 2006@LM_DEBUG@(55460|1) Starting Message_Block_Test test
at Wed Aug 23 2006 16:52:0
0.745814
Aug 23 16:52:00.746 2006@LM_DEBUG@(1) threads = 4
Aug 23 16:52:00.746 2006@LM_DEBUG@(1) Start Message_Block_Test using Default
allocation strategy
Aug 23 16:52:00.748 2006@LM_DEBUG@(515) starting svc() method
Aug 23 16:52:00.748 2006@LM_DEBUG@(258) starting svc() method
Aug 23 16:52:00.748 2006@LM_DEBUG@
(1) sending shutdown message
Aug 23 16:52:00.748 2006@LM_DEBUG@
(1) end producer
Aug 23 16:52:00.748 2006@LM_DEBUG@(1) waiting for worker tasks to finish...
Aug 23 16:52:00.748 2006@LM_DEBUG@(1) destroying worker tasks
======= End Log File

auto_run_tests: tests/Message_Queue_Test
auto_run_tests_finished: test/Message_Queue_Test Time:1s Result:0
Error: (log/Message_Queue_Test.log): enqueue: Invalid argument
Error: (log/Message_Queue_Test.log): dequeue_head: Invalid argument

auto_run_tests: tests/Message_Queue_././Message_Queue_Test_Ex
ERROR: <Message_Queue_Test_Ex> exited with coredump from signal 11 : SEGV
auto_run_tests_finished: test/Message_Queue_Test_Ex Time:1s Result:0
Error: Message_Queue_Test_Ex dumped core
Error (log/Message_Queue_Test_Ex.log): no line with 'Ending'
======= Begin Log File
Aug 23 16:52:03.811 2006@LM_DEBUG@(55466|1) Starting Message_Queue_Test_Ex
test at Wed Aug 23 2006 16:52:03.811960
Aug 23 16:52:03.814 2006@LM_DEBUG@Timed dequeue test: OK
Aug 23 16:52:03.858 2006@LM_INFO@ACE_Message_Queue_Ex<ACE_NULL_SYNCH>,
single thread: 10000 messages took 33 msec (0.003300 msec/message)
Aug 23 16:52:03.877 2006@LM_INFO@ACE_Message_Queue_Ex<ACE_SYNCH>: 10000
messages took 3152383431 msec (315238.343100 msec/message)
======= End Log File

auto_run_tests: tests/Process_Manual_Event_Test
ERROR: Process_Manual_Event_Test timedout
Error: Process_Manual_Event_Test FAILED (time out)
auto_run_tests_finished: test/Process_Manual_Event_Test Time:400s Result:-1
Error (log/Process_Manual_Event_Test.log): no line with 'Ending'
======= Begin Log File
Aug 23 16:52:44.365 2006@LM_DEBUG@(53186|1) Starting
Process_Manual_Event_Test test at Wed Aug 23 2006 16:52:44.365994
Aug 23 16:52:44.382 2006@LM_DEBUG@Parent spawned child process with pid =
57384.
Aug 23 16:52:44.383 2006@LM_DEBUG@(53186) Begin ping-pong
Aug 23 16:52:44.384 2006@LM_DEBUG@(53186) Ping
======= End Log File
Error (Process_Manual_Event_Test-child.log): no line with 'Ending'
Error (Process_Manual_Event_Test-child.log): Number of 'Starting' does not
match number of 'Ending' (1!= 0)
======= Begin Sublog File Process_Manual_Event_Test-child.log
Aug 23 16:52:44.384 2006@LM_DEBUG@(57384|1) Starting
Process_Manual_Event_Test-child test at Wed Aug 23
 2006 16:52:44.384052
Aug 23 16:52:44.384 2006@LM_DEBUG@(57384) Begin ping-pong
Aug 23 16:52:44.384 2006@LM_DEBUG@(57384) Pong
======= End Sublog File

auto_run_tests: tests/Recursive_Condition_Test
auto_run_tests_finished: test/Recursive_Condition_Test Time:20s Result:0
Error: (log/Recursive_Condition_Test.log): (258) waiter found protected_int
1
Error: (log/Recursive_Condition_Test.log): (515) waiter found protected_int
1
Error: (log/Recursive_Condition_Test.log): (772) waiter found protected_int
3
Error: (log/Recursive_Condition_Test.log): (1029) waiter found protected_int
3
Error: (log/Recursive_Condition_Test.log): (1286) waiter found protected_int
3
Error: (log/Recursive_Condition_Test.log): (1543) waiter found protected_int
3

auto_run_tests: tests/Signal_Test
auto_run_tests_finished: test/Signal_Test Time:3s Result:0
Error (Signal_Test-child.log): Number of 'Starting' does not match number of
'Ending' (3 != 2)
======= Begin Sublog File Signal_Test-child.log
Aug 23 17:01:36.923 2006@LM_DEBUG@(59354|1) Starting Signal_Test-child test
at Wed Aug 23 2006 17:01:36.923201
Aug 23 17:01:36.923 2006@LM_DEBUG@(59354|1) **** test 1: handle signals
synchronously in separate thread
Aug 23 17:01:36.923 2006@LM_DEBUG@(59354|1) spawning worker thread
Aug 23 17:01:36.924 2006@LM_DEBUG@(59354|1) spawning signal handler thread
Aug 23 17:01:36.924 2006@LM_DEBUG@(59354|1) Ending Signal_Test-child test at
Wed Aug 23 2006 17:01:36.924462

Aug 23 17:01:36.933 2006@LM_DEBUG@(19328|1) Starting Signal_Test-child test
at Wed Aug 23 2006 17:01:36.933329
Aug 23 17:01:36.933 2006@LM_DEBUG@(19328|1) **** test 2: handle signals
synchronously in this thread
Aug 23 17:01:36.933 2006@LM_DEBUG@(19328|1) spawning worker thread
Aug 23 17:01:36.940 2006@LM_DEBUG@(19328|258) sleeping for 2 seconds
Aug 23 17:01:38.940 2006@LM_DEBUG@(19328|258) sending SIGHUP to parent
process 59106
Aug 23 17:01:38.940 2006@LM_DEBUG@(19328|258) sleeping for 2 seconds
Aug 23 17:01:38.952 2006@LM_DEBUG@(19328|1) synchronous signal handler done
Aug 23 17:01:38.952 2006@LM_DEBUG@(19328|1) Ending Signal_Test-child test at
Wed Aug 23 2006 17:01:38.952947

Aug 23 17:01:38.961 2006@LM_DEBUG@(59356|1) Starting Signal_Test-child test
at Wed Aug 23 2006 17:01:38.961491
Aug 23 17:01:38.961 2006@LM_DEBUG@(59356|1) **** test 3: handle signals
asynchronously in this thread
Aug 23 17:01:38.961 2006@LM_DEBUG@(59356|1) sleeping for 2 seconds
======= End Sublog File

auto_run_tests: tests/SOCK_Connector_Test
auto_run_tests_finished: test/SOCK_Connector_Test Time:1s Result:0
Warning: (log/SOCK_Connector_Test.log): Immediate success/fail; test not
completed
======= Begin Log File
Aug 23 17:01:39.936 2006@LM_DEBUG@(59108|1) Starting SOCK_Connector_Test
test at Wed Aug 23 2006 17:01:39.936512
Aug 23 17:01:39.942 2006@LM_DEBUG@Testing to host "localhost"
Aug 23 17:01:39.944 2006@LM_DEBUG@Proper fail: Connection refused
Aug 23 17:01:39.944 2006@LM_DEBUG@Testing to host "localhost", port 7
Aug 23 17:01:39.944 2006@LM_WARNING@Immediate success/fail; test not
completed
Aug 23 17:01:39.944 2006@LM_DEBUG@(59108|1) Ending SOCK_Connector_Test test
at Wed Aug 23 2006 17:01:39.944501

auto_run_tests: tests/Thread_Pool_Reactor_Resume_Test
terminate called after throwing an instance of 'std::ios_base::failure'
  what():  basic_ios::clear
auto_run_tests_finished: test/Thread_Pool_Reactor_Resume_Test Time:4s
Result:0
Error: Thread_Pool_Reactor_Resume_Test dumped core

auto_run_tests: tests/Thread_Pool_Reactor_Test
terminate called after throwing an instance of 'std::ios_base::failure'
  what():  basic_ios::clear
auto_run_tests_finished: test/Thread_Pool_Reactor_Test Time:4s Result:0
Error: Thread_Pool_Reactor_Test dumped core

auto_run_tests: tests/Recursive_Condition_Bug_Test
ERROR: <Recursive_Condition_Bug_Test> exited with coredump from signal 4 :
ILL
auto_run_tests_finished: test/Recursive_Condition_Bug_Test Time:1s Result:0
Error: Recursive_Condition_Bug_Test dumped core


        OTHER (please specify)?

    SYNOPSIS:

    DESCRIPTION:

    REPEAT BY:
Each time the tests are executed with run_test.pl

    SAMPLE FIX/WORKAROUND:
None 


0
Pierre
8/24/2006 5:50:40 AM
comp.soft-sys.ace 20326 articles. 1 followers. marlow.andrew (167) is leader. Post Follow

0 Replies
1258 Views

Similar Articles

[PageSpeed] 18

Reply:

Similar Artilces:

[ace-bugs] test program failed on running Static library of ACE 5.4 / 5.4.1 / 5.3.1 on AMD 64 Windows platform
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C4D5E6.73D906B6 Content-Type: text/plain ACE VERSION: 5.4 / 5.4.1 / 5.3.1 HOST MACHINE and OPERATING SYSTEM: Windows 2003 Server - AMD64 bit platform: TARGET MACHINE and OPERATING SYSTEM, if different from HOST: COMPILER NAME AND VERSION (AND PATCHLEVEL): Compiler Version 14.00.40310.23 for AMD64 using Microsoft Platform SDK Linker Version 8.00.40310.23 using Microsoft Platform SDK CONTEN...

[ace-bugs] RE: test program failed on running Static library of ACE 5.4 / 5.4.1 / 5.3.1 on AMD 64 Windows platform
Hi, Thanks for using the PRF form. Do I understand correctly you are using Windows 64 bit and the 64bit Microsoft compiler? This is a platform that is not tested yet and it seems that there are still some problems. Because such a simple program doesn't work maybe compiler/linker options could be the problem. We have here AMD64 with SuSE 92 Linux without problems, AMD64 with a normal windows xp and the normale vc71 compiler also doesn't have problems. Maybe you can investigate this and supply patches, or else look at http://www.cs.wustl.edu/~schmidt/commercial-support.html for companies that deliver ACE/TAO support. We as Remedy IT can also solve this for you, see www.theaceorb.nl for our services. Regards, Johnny Willemsen Remedy IT Leeghwaterstraat 25 2811 DT Reeuwijk The Netherlands www.theaceorb.nl / www.remedy.nl > ACE VERSION: 5.4 / 5.4.1 / 5.3.1 > > HOST MACHINE and OPERATING SYSTEM: > Windows 2003 Server - AMD64 bit platform: > > TARGET MACHINE and OPERATING SYSTEM, if different from HOST: > COMPILER NAME AND VERSION (AND PATCHLEVEL): > Compiler Version 14.00.40310.23 for AMD64 using Microsoft Platform SDK > Linker Version 8.00.40310.23 using Microsoft Platform SDK > > CONTENTS OF $ACE_ROOT/ace/config.h [if you use a link to > a platform- > specific file, simply state which one]: > config.h > > CONTENTS OF > $A...

[ace-bugs] RE: test program failed on running Static library of ACE 5.4 / 5. 4.1 / 5.3.1 on AMD 64 Windows platform
Hi Johnny, Thanks for your response. Actually Mr. Dougs response to check with ACE version 5.4.2 worked for me and I am not getting this corruption issues with this version of ACE. There were few minor compilation issues with this release of ACE but they were quite easy to resolve. Regards, Meenakshi -----Original Message----- From: Johnny Willemsen [mailto:jwillemsen@remedy.nl] Sent: Sunday, November 28, 2004 11:46 PM To: Meenakshi Vohra; ace-bugs@cs.wustl.edu Subject: RE: test program failed on running Static library of ACE 5.4 / 5.4.1 / 5.3.1 on AMD 64 Windows platform ...

Re: [ace-users] [ACE 5.5] Upgrade from ACE 5.4.7 to ACE 5.5 #2
Hi Ishay, >> Sorry, we are using DevStudio 7.1 (2003) We use this too. Please see ACE_ROOT/tests/Time_Value_Test.cpp for lots of examples that use ACE_Time_Value with integers. Please see if this works on your OS/compiler platform. Thanks, Doug >> ~ Ishay >> >> Software Architect >> Onigma Ltd. >> Tel: +972-3-6877315 >> Fax: +972-3-6877128 >> Mobile: +972-54-2325090 >> Email: ishay@onigma.com >> >> -----Original Message----- >> From: Johnny Willemsen [mailto:jwillemsen@remedy.nl] >> Sent: Tuesday, March 07, 2006 2:42 PM >> To: 'Ishay Green'; ace-users@cs.wustl.edu >> Subject: RE: [ace-users] [ACE 5.5] Upgrade from ACE 5.4.7 to ACE 5.5 >> >> Hi, >> >> > ACE VERSION: 5.5 >> >> Thanks for using the PRF form. >> >> > HOST MACHINE and OPERATING SYSTEM: >> > >> > Intel, WindowsXp, Windows 2003 >> >> An important bit information is missing, which compiler did you use. >> >> > AREA/CLASS/EXAMPLE AFFECTED: >> > The only problem we encountered was a compilation error >> > when construction ACE_Time_Value. >> > >> > The ACE_Time_Value cannot be constructed anymore from an integer. >> > >> > For example: ACE_Time_Value( 5 ) --> Compile error >>...

RE: [ace-users] [ACE 5.5] Upgrade from ACE 5.4.7 to ACE 5.5 #2
Hi, Sorry, we are using DevStudio 7.1 (2003) ~ Ishay Software Architect Onigma Ltd. Tel: +972-3-6877315 Fax: +972-3-6877128 Mobile: +972-54-2325090 Email: ishay@onigma.com -----Original Message----- From: Johnny Willemsen [mailto:jwillemsen@remedy.nl] Sent: Tuesday, March 07, 2006 2:42 PM To: 'Ishay Green'; ace-users@cs.wustl.edu Subject: RE: [ace-users] [ACE 5.5] Upgrade from ACE 5.4.7 to ACE 5.5 Hi, > ACE VERSION: 5.5 Thanks for using the PRF form. > HOST MACHINE and OPERATING SYSTEM: > > Intel, WindowsXp, Windows 2003 An important bit information is missing, which compiler did you use. > AREA/CLASS/EXAMPLE AFFECTED: > The only problem we encountered was a compilation error > when construction ACE_Time_Value. > > The ACE_Time_Value cannot be constructed anymore from an integer. > > For example: ACE_Time_Value( 5 ) --> Compile error Great to hear things work without problems. This errors sounds strange, we do have test cases like this in tests/Time_Value_Test.cpp. We do have made all constructors of ACE_Time_Value explicit. As a result if you have a method that expects a ACE_Time_Value&, you just can't pass for example 5, you have to pass an ACE_Time_Value(5). Regards, Johnny Willemsen Remedy IT Postbus 101 2650 AC Berkel en Rodenrijs The Netherlands www.theaceorb.nl / www.remedy.nl ...

ACE migration from 5.3 to 5.4.1 ACE_Svc_Tuple does not exist in ACE 5.4.1
To: ace-bugs@cs.wustl.edu Subject: [area]: [synopsis] ACE VERSION: 5.4.1 HOST MACHINE and OPERATING SYSTEM: (Red Hat Linux 3.2.2-5 TARGET MACHINE and OPERATING SYSTEM, if different from HOST: COMPILER NAME AND VERSION (AND PATCHLEVEL): ACE_wrappers]$ gcc --version gcc (GCC) 3.2.2 20030222 (Red Hat Linux 3.2.2-5) Copyright (C) 2002 Free Software Foundation, Inc. make static_libs=1 shared_libs=1 inline=1 threads=1 exceptions=1 fast=1 ssl=1 CONTENTS OF $ACE_ROOT/ace/config.h ln -s $ACE_ROOT/ace/config-linux.h $ACE_ROOT/ace/config.h CON...

[ace-users] Re: Error while ACE 5.3.1 or 5.4.1 compiling and installing by MinGW 3.3.3
Hi Vitaly, Please upgrade to ACE 5.4.4, which you can download from http://deuce.doc.wustl.edu/Download.html since I think that is more likely to work with MinGW 3.3.3. Johnny, can you confirm/deny this please? Thanks, Doug >> Hi, >> I have installed MinGW packages: >> >> binutils-2.13.90-20030111-1.tar.gz >> gcc-core-3.3.3-20040217-1.tar.gz >> gcc-g++-3.3.3-20040217-1.tar.gz >> mingw-runtime-3.3.tar.gz >> w32api-2.5.tar.gz >> >> Also I've configured environment due to ACE-INSTALL.htm...

[ace-users] [ACE 5.5] Upgrade from ACE 5.4.7 to ACE 5.5
This is a multi-part message in MIME format. --Boundary_(ID_ogLNJ2XjtOnI/qoGYuqYNQ) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT ACE VERSION: 5.5 HOST MACHINE and OPERATING SYSTEM: Intel, WindowsXp, Windows 2003 AREA/CLASS/EXAMPLE AFFECTED: Our team has upgraded from ACE 5.4.7 to ACE 5.5. I am submitting this email as a service for the ace members that considure upgrading to ACE 5.5 and using the same platform and features we are using from the ACE Frameworks library. After running a regression test the upgrade seemed to work without any problems. The only problem we encountered was a compilation error when construction ACE_Time_Value. The ACE_Time_Value cannot be constructed anymore from an integer. For example: ACE_Time_Value( 5 ) --> Compile error DESCRIPTION: We are using ACE_WIN32_Proactor with sockets, pipes and directory changes. BOTTOM LINE: If you are an ace user who are using the same platform and architecture you could upgrade to the new framework knowing that somewhere in the world (Israel/Onigma) the upgrade worked perfectly and nightly. ~ Ishay Software Architect Onigma Ltd. Tel: +972-3-6877315 Fax: +972-3-6877128 Mobile: +972-54-2325090 Email: ishay@onigma.com --Boundary_(ID_ogLNJ2XjtOnI/qoGYuqYNQ) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BI...

[ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi,all I rebuild the ACE package according the instruction above,but get the same result. my platform_macros.GNU file has the following lines: templates = implicit include $(ACE_ROOT)/include/makeinclude/platform_sunos5_sunc++.GNU When i rebuild the ACE library,get the following compile errors: $ make inline=0 -j 2 -k -f GNUmakefile.ACE .... .... CC -mt -g -DSUN_CC_HAS_PVFC_BUG -I/export/home/hua/DevTools/ACE_wrappers -DACE_HAS_EXCEPTIONS -DACE_NO_INLINE -I.. -DACE_HAS_ACE_TOKEN -DACE_HAS_ACE_SVCCONF -DACE_BUILD_DLL -c -KPIC -o .shobj/OS_NS_sys_stat.o OS_NS_sys_...

[ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi, ACE VERSION: 5.4.3 HOST MACHINE and OPERATING SYSTEM: Solaris 10 x86 TARGET MACHINE and OPERATING SYSTEM, if different from HOST: COMPILER NAME AND VERSION (AND PATCHLEVEL): Sun Studio 9 (Sun CC 5.6) CONTENTS OF $ACE_ROOT/ace/config.h [if you use a link to a platform- specific file, simply state which one]: #define ACE_HAS_STANDARD_CPP_LIBRARY 1 #define ACE_USES_STD_NAMESPACE_FOR_STDCPP_LIB 1 #include "ace/config-sunos5.9.h" CONTENTS OF $ACE_ROOT/include/makeinclude/platform_macros.GNU (unless ...

Re: [ace-users] g++ 3.4.3 and ACE 5.5 & TAO 1.5
Hi, Please upgrade to ACE/TAO 1.5.3 which you can obtain from http://download.dre.vanderbilt.edu. Regards, Johnny Willemsen Remedy IT Postbus 101 2650 AC Berkel en Rodenrijs The Netherlands www.theaceorb.nl / www.remedy.nl "M@uro!!" <mauro.gaddo@gmail.com> wrote in message news:<1161692263.239945.111960@m7g2000cwm.googlegroups.com>... > During compiling on HP-UX 11.11 with g++ i have the following error: > > g++ -DHAVE_CONFIG_H -I../.. -I.. -DACE_HAS_ACE_TOKEN > -DACE_HAS_ACE_SVCCONF -DACE_BUILD_DLL -DHPUX_VERS=1111 -w -W -Wall > -Wpointer-arith -g -O2 -pthread -pipe -I. -I.. -MT > libACE_la-OS_NS_stdio.lo -MD -MP -MF .deps/libACE_la-OS_NS_stdio.Tpo -c > ../../ace/OS_NS_stdio.cpp -fPIC -DPIC -o .libs/libACE_la-OS_NS_stdio.o > ../../ace/OS_NS_stdio.cpp: In function `int ACE_OS::fprintf(FILE*, > const wchar_t*, ...)': > ../../ace/OS_NS_stdio.cpp:242: error: `::vfwprintf' has not been > declared > > Can someone helps me? > > Thanks!! > M. > ...

RE: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi Steve, > > Is this necessary? I mean make it implicit by default. The > > explicit is > > not even supported, and has no chance to work cleanly. Why > > should we patch > > broken stuff. Just a thought? > > At least for ACE 5.5, Riverace supports the Forte compiler that > requires explicit. After that, we can drop it. Ok. Steve, could you maybe make clear with the build names which builds use explicit templates? Explicit templates in TAO are known to be broken at this moment. Johnny ...

RE: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
> Ok. Steve, could you maybe make clear with the build names > which builds use explicit templates? I'll try to get this clarified. > Explicit templates in TAO are known to be broken at this > moment. None of the tests at Riverace try to build TAO. -Steve ...

Re: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi Jin, Thanks for using the PRF. >> ACE VERSION: 5.4.3 >> >> HOST MACHINE and OPERATING SYSTEM: >> Solaris 10 x86 >> >> TARGET MACHINE and OPERATING SYSTEM, if different from HOST: >> COMPILER NAME AND VERSION (AND PATCHLEVEL): >> Sun Studio 9 (Sun CC 5.6) As we've mentioned several times now, we don't have this compiler installed yet on this hardware platform, so if you want things to be fixed soon I recommend you figure out what's going wrong and send us the patches. Otherwise, pl...

RE: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi, > > > ACE VERSION: 5.4.3 > > > > > > HOST MACHINE and OPERATING SYSTEM: > > > Solaris10 X86 > > > TARGET MACHINE and OPERATING SYSTEM, if different from HOST: > > > COMPILER NAME AND VERSION (AND PATCHLEVEL): > > > Compiler: SUN CC 5.6 > ^^^^^^^^^^^^^^^^^^^^^^^^ > > I don't think the DOC group supports this compiler anymore.. More > particularly this compiler is buggy and you may land up with > unresolved > symbols even if you get past this pa...

Re: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi Everyon: My SunBlade 150 is back up and available, and has a Sun CC license, though I don't have a lot of bandwidth to admin it. Bala know where it is and has the root password. I'll probably move it into the server room once I have a chance to talk to Dan about it, but I my be out of town this week. [dhinton@blade DRM]$ uname -a SunOS blade 5.9 Generic_112233-03 sun4u sparc SUNW,Sun-Blade-100 Solaris [dhinton@blade DRM]$ CC -V CC: Forte Developer 7 C++ 5.4 2002/03/09 [dhinton@blade DRM]$ gcc --version gcc (GCC) 3.4.2 Copyright (C) 2004 Free Software Foundation, ...

Re: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Johnny- > Ok, the problem is in platform_sunos5_sunc++.GNU, when a not known forte > version is found, it defaults to explicit. I am updating right now, for 4.2 > and 5.3 we default to explicit, for all others to implicit Is this necessary? I mean make it implicit by default. The explicit is not even supported, and has no chance to work cleanly. Why should we patch broken stuff. Just a thought? > Qinghuajin and other Forte 9 users, you can work around this by added the > following line to your platform_macros.GNU file. > templates = implicit This is until w...

RE: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi, > > > I don't think the DOC group supports this compiler anymore.. More > > > particularly this compiler is buggy and you may land up with > > > unresolved > > > symbols even if you get past this part. > > > > I missed the compiler version. But, Forte 8 gives output of > SUN C++ 5.5. Ok, the problem is in platform_sunos5_sunc++.GNU, when a not known forte version is found, it defaults to explicit. I am updating right now, for 4.2 and 5.3 we default to explicit, for all others to implicit Qinghuajin and other Forte...

RE: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi, > >> It's almost up. There are some issues with installing software as > >> we don't have the media in a compatible form yet. We also don't > >> have Sun CC, and we need to purchase a licence if we need to > >> support Sun CC. > > Ok, that's fine - thanks for the update. I think some other folks > (e.g., LMCO ATL and Remedy) have Solaris 9/10 and Sun CC, so we may > not need to worry about running Sun CC on our machine. Johnny/Gautam, > can you folks please confirm/deny whether you've got Sun CC on Solar...

Re: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Johnny- > > > > ACE VERSION: 5.4.3 > > > > > > > > HOST MACHINE and OPERATING SYSTEM: > > > > Solaris10 X86 > > > > TARGET MACHINE and OPERATING SYSTEM, if different from HOST: > > > > COMPILER NAME AND VERSION (AND PATCHLEVEL): > > > > Compiler: SUN CC 5.6 > > ^^^^^^^^^^^^^^^^^^^^^^^^ > > > > I don't think the DOC group supports this compiler anymore.. More > > particularly this compiler is buggy and you may land up with ...

RE: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi, > > Ok, the problem is in platform_sunos5_sunc++.GNU, when a > not known forte > > version is found, it defaults to explicit. I am updating > right now, for 4.2 > > and 5.3 we default to explicit, for all others to implicit > > Is this necessary? I mean make it implicit by default. The > explicit is > not even supported, and has no chance to work cleanly. Why > should we patch > broken stuff. Just a thought? I have thought also about this, but maybe there are users around we don't know if. We can drop all this after x.5 is released, until that time, I just keep it there, just as we have a lot of other stuff that is probably broken. > > Qinghuajin and other Forte 9 users, you can work around > this by added the > > following line to your platform_macros.GNU file. > > templates = implicit > > This is until we release x.4.4., right? Yes, with x.4.4 this will be done correctly. Johnny ...

Re: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi Jin, >> I rebuild the ACE package according the instruction above,but get >> the same result. It doesn't look to me like you've added -DACE_HAS_X86_STAT_MACROS to the build-line as recommended by Johnny Willemsen. >> my platform_macros.GNU file has the following lines: >> >> templates = implicit >> include $(ACE_ROOT)/include/makeinclude/platform_sunos5_sunc++.GNU >> >> When i rebuild the ACE library,get the following compile errors: >> $ make inline=0 -j 2 -k -f GNUmakefile.ACE >> ... >&...

RE: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
> > Ok, the problem is in platform_sunos5_sunc++.GNU, when a > not known forte > > version is found, it defaults to explicit. I am updating > right now, for 4.2 > > and 5.3 we default to explicit, for all others to implicit This sounds good. > Is this necessary? I mean make it implicit by default. The > explicit is > not even supported, and has no chance to work cleanly. Why > should we patch > broken stuff. Just a thought? At least for ACE 5.5, Riverace supports the Forte compiler that requires explicit. After that, we can drop it....

Re: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi > > ACE VERSION: 5.4.3 > > > > HOST MACHINE and OPERATING SYSTEM: > > Solaris10 X86 > > TARGET MACHINE and OPERATING SYSTEM, if different from HOST: > > COMPILER NAME AND VERSION (AND PATCHLEVEL): > > Compiler: SUN CC 5.6 ^^^^^^^^^^^^^^^^^^^^^^^^ I don't think the DOC group supports this compiler anymore.. More particularly this compiler is buggy and you may land up with unresolved symbols even if you get past this part. My $0.02. Thanks Bala > > Make: ...

RE: [ace-users] [ACE 5.5] Upgrade from ACE 5.4.7 to ACE 5.5
Hi, > ACE VERSION: 5.5 Thanks for using the PRF form. > HOST MACHINE and OPERATING SYSTEM: > > Intel, WindowsXp, Windows 2003 An important bit information is missing, which compiler did you use. > AREA/CLASS/EXAMPLE AFFECTED: > The only problem we encountered was a compilation error > when construction ACE_Time_Value. > > The ACE_Time_Value cannot be constructed anymore from an integer. > > For example: ACE_Time_Value( 5 ) --> Compile error Great to hear things work without problems. This errors sounds strange, we do have test cases like this in tests/Time_Value_Test.cpp. We do have made all constructors of ACE_Time_Value explicit. As a result if you have a method that expects a ACE_Time_Value&, you just can't pass for example 5, you have to pass an ACE_Time_Value(5). Regards, Johnny Willemsen Remedy IT Postbus 101 2650 AC Berkel en Rodenrijs The Netherlands www.theaceorb.nl / www.remedy.nl ...

Web resources about - [ace-users] Tests failed : ACE 5.5.2 - AIX 5.3 - GCC 4.1.1 - comp.soft-sys.ace

Samsung Galaxy Ace 4 User Reviews
Samsung Galaxy Ace 4 reviews written by Phone Arena users. You can read the opinion of each user and how they rate the phone in 11 categories. ...

Samsung Galaxy Ace 3 official: iPhone-alike size for the new user
Samsung has revealed another in its Galaxy series, the Galaxy Ace 3, now targeting entry-level smartphone users who want a pocket-friendly 4-inch ...

Resources last updated: 3/5/2016 6:49:13 AM