At 04:02 PM 11/2/99 , Carl McNamee wrote:
>Ok, I recreated the scenario and now have the following stack trace. Can
>anyone tell me what is going on?
Shooting strictly from the hip and making a few educated guesses:
> PC=a.0015f70c enable_int+$2c
>NM* 0) SP=418587b0 RP=a.002a4b98
>notify_dispatcher.block_current_process+$324
>NM 1) SP=418587b0 RP=a.002a703c notify_dispatcher+$264
>NM 2) SP=41858730 RP=a.0018e3e4 sem_block.wait_for_resource+$1c4
>NM 3) SP=41858630 RP=a.0018e5fc sem_block+$178
The above shows that the process is blocked on a semaphore.
>NM 4) SP=41858570 RP=a.001669a4 joint_lock_path+$34
>NM 5) SP=41858470 RP=a.004a4098 xm_deallocaterecord+$30c
>NM 6) SP=41858428 RP=a.004a5c34 xm_end_user_trans+$1c4
>NM 7) SP=41858368 RP=a.00484d48 xm_w_unlock_and_copyai_var+$2b0
The above seems to indicate that the Transaction Manager *is* active in
this case.
>NM 8) SP=418582a8 RP=a.005cd1cc disc_sm_finish_write+$98
>NM 9) SP=41858228 RP=a.005cd100 ?disc_sm_finish_write+$8
That a call to Storage Management which is responsible for managing memory
mapped disc access to disc including such things as flushing pages to disc.
> export stub: 29c.002f5484 putdetail_340+$3048
>NM a) SP=41858068 RP=29c.002f7480 nmdbput+$17c4
>NM b) SP=41858008 RP=29c.002680e0 nbput+$15c
>NM c) SP=418547d0 RP=29c.00267f58 ?nbput+$8
> export stub: 29c.010947f0 dbput+$3fc
>NM d) SP=418546d0 RP=29c.01094368 ?dbput+$8
The above is a call to dbput against a detail set.
> export stub: 188.00088ad8
>NM e) SP=41853450 RP=188.00088a40
The above seems to be a procedure in an XL.
The rest of the stack trace is code directly in the program.
> export stub: 2bc8.0007fbac
>NM f) SP=418533d0 RP=2bc8.0009a448
>NM 10) SP=418531b0 RP=2bc8.000a9434
>NM 11) SP=41852f88 RP=2bc8.000b4ee0
>NM 12) SP=41852d68 RP=2bc8.00081128
>NM 13) SP=41852b48 RP=2bc8.0009c258
>NM 14) SP=41852928 RP=2bc8.0009c7bc
>NM 15) SP=41852708 RP=2bc8.00100d4c
>NM 16) SP=418524e8 RP=2bc8.00101114
>NM 17) SP=418522c8 RP=2bc8.00000000
> (end of NM stack)
--
Jeff Woods
[log in to unmask]
