Re: [Fwd: tests/rr-server core dumps multi-processor]

Paul Caffrey <[email protected]> Thu, 20 Feb 2003 13:18:48 +0000
Newsgroups gmane.network.beep.roadrunner.general
Message-ID <[email protected]>
Jonas

Further testing of new version results below.

Once again thanks

Paul

Running on 4 cpu machine, client core dumps after ~ 3 hours

server stays up and running

(process:10205): RR-CRITICAL **: file rr-message-start.c: line 365 
(rr_message_start_done): assertion `RR_IS_MESSAGE_START (start)' failed
The string was successfully transferred
The string was successfully transferred
The string was successfully transferred
The string was successfully transferred
The string was successfully transferred
The string was successfully transferred
The string was successfully transferred
The string was successfully transferred
The string was successfully transferred
Segmentation Fault (core dumped)
(gdb) bt
#0  0xff07b9a4 in mutex_unlock () from /usr/lib/libthread.so.1
#1  0xff36538c in rr_waiter_wait (waiter=0x116388, error=0xfe705bc4)
     at rr-waiter.c:109
#2  0xff36b350 in rr_message_start_wait_for_reply (start=0x3f8f0,
     error=0xfe705bc4) at rr-message-start.c:380
#3  0xff35fc08 in rr_manager_start_multiv (manager=0x2be08,
     server_name=0x3f8f0 "", error=0xfe705bc4, args=0xfe705b48)
     at rr-manager.c:811
#4  0xff35f908 in rr_manager_start_multi (manager=0x2be08, server_name=0x0,
     error=0xfe705bc4) at rr-manager.c:742
#5  0xff364884 in rr_connection_start (connection=0x2b230, server_name=0x0,
     profile_type=176104, config_data=0x0, error=0xfe705bc4)
     at rr-connection.c:984
#6  0x00011278 in do_tests (connection=0x2b230) at rr-client.c:28
#7  0x000113d0 in my_thread (data=0x2b230) at rr-client.c:55
#8  0xff246c6c in g_thread_create_proxy (data=0x0) at gthread.c:551


On itchy, single cpu machine the client crashes after ~ 3 hours
No error message, Bus Error (core dumped)
(gdb) bt
#0  0xff222604 in g_io_create_watch (channel=0x3cce0, condition=G_IO_OUT)
     at giochannel.c:455
#1  0xff375f44 in add_watch_full (channel=0x3cce0, priority=0,
     condition=G_IO_OUT, func=0xff377388 <out_event>, user_data=0x2af98,
     notify=0xff376634 <out_removed>) at rr-tcpconnection.c:99
#2  0xff376b50 in enable_output (conn=0x2af98) at rr-tcpconnection.c:383
#3  0xff37325c in rr_connection_enable_output (connection=0x2af98)
     at rr-connection.c:430
#4  0xff372a4c in rr_connection_register_sender (connection=0x2af98,
     channel=0x2bb70) at rr-connection.c:201
#5  0xff369a6c in send_helper (channel=0x2bb70, object=0x432a4,
     error=0xfe9fbe54) at rr-channel.c:262
#6  0xff369b78 in rr_channel_send_message (channel=0x2bb70, 
message=0x432a4,
     error=0xfe9fbe54) at rr-channel.c:285
#7  0xff370040 in rr_manager_close_channel (manager=0x2bb70, 
channel=0x432a4,
     code=200, xml_lang=0x12628 "sv", diagnostic=0x12630 "Foo",
     error=0xfe9fbe54) at rr-manager.c:893
#8  0xff36b010 in rr_channel_close (channel=0x425d4, code=200,
     xml_lang=0x12628 "sv", diagnostic=0x12630 "Foo", error=0xfe9fbe54)
     at rr-channel.c:756
#9  0x00011368 in do_tests (connection=0x425d4) at rr-client.c:44
#10 0x000113d0 in my_thread (data=0x2af98) at rr-client.c:55
#11 0xff246c6c in g_thread_create_proxy (data=0x0) at gthread.c:551

PS

On third machine, single cpu machine also, still running no problems.