[Dpcl-develop] Using 'diag' test

[Steve C. <sl...@sg...>]

    Hello, DPCL'ers. I am using DPCL/Dyninst on ia64 and, for some
  time now, have been trying to get the 'diag' (eut_diag) sample DPCL
  test running. It seems to (non-deterministically) be dying in the
  daemon_RT shared memory code, to wit:

              #0  shmFObjectAllocV (buffer=0x2000000000f15000, shm_key=
                     {daemon_address = 0x2000000000e15000, process_address = 0x2000000000f15000}, 
                   object_number=1, object_holder=0x2000000000e263c8, rc=0x60000fffffff8100)
                   at ../src/os/linux/ShmManager.C:687
               687            *p_free_object = 
               (gdb) where
               #0  shmFObjectAllocV (buffer=0x2000000000f15000, shm_key=
                     {daemon_address = 0x2000000000e15000, process_address = 0x2000000000f15000}, 
                   object_number=1, object_holder=0x2000000000e263c8, rc=0x60000fffffff8100)
                   at ../src/os/linux/ShmManager.C:687
               #1  0x2000000000e11090 in shm_processObjectAllocV (shm_key=
                     {daemon_address = 0x2000000000e15000, process_address = 0x2000000000f15000}, 
                   object_number=0, object_holder=0x2000000000e263c8, rc=0x60000fffffff8100)
                   at ../src/os/linux/ShmManagerAPI_app.C:48
               #2  0x2000000000e119d0 in Ais_send (msg_handle_id=0x2000000000f225a4 "", 
                   message=0x200000000083e320, message_size=30) at ../src/os/linux/ShmMessageAPI_app.C:319
               #3  0x2000000000e11670 in Ais_send_int (msg_handle_id=0x2000000000f225a4 "", 
                   message=0x200000000083e320, message_size=30) at ../src/os/linux/ShmMessageAPI_app.C:85
               #4  0x200000000083e3e0 in DYNINSTstaticHeap_4M_anyHeap_1 ()
                  from /scratch/slc/dpcl-install/lib/libdyninstAPI_RT.so.1

  This walkback from gdb is, itself, suspicious, but about all I have available.
  Again, the failure doesn't happen every time. If I tweak 'diag' (eut_diag.C)
  in a small, seemingly innocuous, way, then things work. If I put any sort of
  debug prints in place, then the SEGV doesn't appear. It really seems like a
  timing thing, but I can't finger the culprit.

    This is admittedly a fishing expedition. Does 'diag' have some sort of known
   race condition, or flaky behaviour? Just fishing....

                                                 SteveC - SGI Tools/Compilers