[torqueusers] segfaulting pbs_moms: torque-2.3.6-2cri.x86_64

[Martin MOKREJŠ]

Douglas McNab wrote:
> Hi Folks,
> 
> Thanks for all your replies.  I have thought that mixing versions was a
> little unsafe.  However,  I am a little confused why they can work
> together for a period of time and then decided to segfault when the
> server pings the mom's.  So to find an explantion I have built a debug
> build.  After debugging my segfaulting moms torque-2.3.6-2cri.x86_64
> further with a debug build I seem to move a little closer to the problem.
> 
> Program received signal SIGSEGV, Segmentation fault.
> mom_server_find_by_ip (search_ipaddr=177078032) at mom_server.c:450
> 450           ipaddr = ntohl(addr->sin_addr.s_addr);
> (gdb) where
> #0  mom_server_find_by_ip (search_ipaddr=177078032) at mom_server.c:450
> #1  0x000000000041965e in mom_server_valid_message_source (stream=0) at
> mom_server.c:2022
> #2  0x0000000000419870 in is_request (stream=0, version=1,
> cmdp=0x7fffcb2774d8) at mom_server.c:2125
> #3  0x0000000000416997 in do_rpp (stream=0) at mom_main.c:5351
> #4  0x0000000000416a52 in rpp_request (fd=<value optimized out>) at
> mom_main.c:5408
> #5  0x00002ae6c4678bc8 in wait_request (waittime=<value optimized out>,
> SState=0x0) at ../Libnet/net_server.c:469
> #6  0x0000000000416c1d in main_loop () at mom_main.c:8046
> #7  0x0000000000416ee1 in main (argc=1, argv=0x7fffcb277bc8) at
> mom_main.c:8148
> (gdb) print ipaddr
> No symbol "ipaddr" in current context.

Try "bt full" command instead in your next gdb session. ;-)

M.