Re: [Dpcl-develop] Using 'diag' test

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

   Some additional debug info provided by gdb (do I dare trust it??) at the
 site of the SEGV per the corefile:

#0  shmFObjectAllocV (buffer=0x2000000000f15000, shm_key=
      {daemon_address = 0x2000000000e15000, process_address = 0x2000000000f15000}, 
    object_number=1, object_holder=0x2000000000e2a750, rc=0x60000fffffff8180)
    at ../src/os/linux/ShmManager.C:826
826	      *p_free_object = 
(gdb) where
#0  shmFObjectAllocV (buffer=0x2000000000f15000, shm_key=
      {daemon_address = 0x2000000000e15000, process_address = 0x2000000000f15000}, 
    object_number=1, object_holder=0x2000000000e2a750, rc=0x60000fffffff8180)
    at ../src/os/linux/ShmManager.C:826
#1  0x2000000000e11340 in shm_processObjectAllocV (shm_key=
      {daemon_address = 0x2000000000e15000, process_address = 0x2000000000f15000}, 
    object_number=1, object_holder=0x2000000000e2a750, rc=0x60000fffffff8180)
    at ../src/os/linux/ShmManagerAPI_app.C:50
#2  0x2000000000e11cb0 in Ais_send (msg_handle_id=0x2000000000f225a4 "", 
    message=0x2000000001f37a20, message_size=30) at ../src/os/linux/ShmMessageAPI_app.C:334
#3  0x2000000000e11950 in Ais_send_int (msg_handle_id=0x2000000000f225a4 "", 
    message=0x2000000001f37a20, message_size=30) at ../src/os/linux/ShmMessageAPI_app.C:89
#4  0x2000000001f37ae0 in ?? ()
Previous frame identical to this frame (corrupt stack?)
(gdb) p p_free_object
$1 = (freeFObjectH **) 0x2000000000e2a758
(gdb) p *p_free_object
$2 = (freeFObjectH *) 0x0
(gdb) p object_holder
$3 = (void **) 0x2000000000e2a750
(gdb) p *object_holder
$4 = (void *) 0x8956726d00f01000
(gdb) p object_counter
$5 = 0
(gdb) p object_number
$6 = 1
(gdb) p memory_buffer
$7 = (memBuffer *) 0x2000000000f01000
(gdb) p page
No symbol "page" in current context.
(gdb) p page->free_space
No symbol "page" in current context.