Can the description area and comments scetion fornt be changed to mono-spaced
Hello Team
Can the description area and comments section font be changed to mono-spaced. User under our project may need to add data for memory dumps etc.. Like the below comment
So the core is confirming just the two competing threads (as before):
(dbx) thread
thread state-k wchan state-u k-tid mode held scope function
$t1 run 0xf1000a00e027bb18 running 120586403 k no sys semop
*$t2 run running 73859303 k no sys _mutex_lock
$t3 run 0xf1000f0a1001d540 blocked 30736467 k no sys _event_sleep
>$t4 run 0x09001000a53efa90 blocked 35651829 k no sys _global_lock_common
$t5 run 0xf1000a00e027cd98 running 32571481 k no sys semop
$t6 run 0xf1000a00e027ce40 running 95748101 k no sys semop
$t7 run 0xf1000a00e027cb98 running 89522217 k no sys semop
$t8 run 0xf1000a00e027c418 running 64422015 k no sys semop
(dbx) thread current 4
warning: Thread is in kernel mode, not all registers can be accessed.
(dbx) where
_global_lock_common(??, ??, ??) at 0x90000000097d83c
_mutex_lock(??, ??, ??) at 0x90000000098b210
mFt_rt_savarea_step_start() at 0x90000002595c65c <- called pthread_mutex_lock
_mFginitdat() at 0x900000025a0c5f8
DSUB5010.init() at 0x900000002410abc
DSUB5010() at 0x9000000024106dc
SPCS0015_0x30a8() at 0x900000002416f30
SPCS0015() at 0x9000000024130d4
.sqloInvokeFnArgs.fdpr.chunk.1(??, ??, ??) at 0x9000000080a7948
sqloLatchCAS64.sqlerInvokeOLEUDF.fdpr.chunk.22(unsigned int,void**,sqleInvokerCB*)(??, ??) at 0x9000000080a7cc4
sqloLatchCAS64.sqlerInvokeOLEUDF.fdpr.chunk.10(unsigned int,void**,sqleInvokerCB*)(??, ??) at 0x900000007dd4474
sqlerFmpListener.fdpr.chunk.28(??, ??, ??, ??, ??) at 0x9000000080bcd1c
sqlerWorkerThreadEntry(void*)(??) at 0x9000000084dc860
0x09001000a53efa70 0000000300000000 0000000111072980 ..............).
0x09001000a53efa80 0000000000000000 0000000000000000 ................ ; pthread should start at 0x09001000a53efa88 based on wchan
0x09001000a53efa90 346700e700000000 0000000000000102 4g.............. ; wchan here
0x09001000a53efaa0 0000000000000000 0000000000000001 ................
0x09001000a53efab0 0000000000000004 000000000000009c ................
0x09001000a53efac0 0000000100000000 0000000000000000 ................
0x09001000a53efad0 09001000a53f4188 09001000a53f0a10 .....?A......?..
0x09001000a53efae0 0000000000000001 0000000000000000 ................
A locked pthread mutex (on AIX) has bits 27-0 of the 32-bit wchan value as the thread ID - so we can see this is thread ID 0x46700e7 = 73859303.
Can the description area and comments section font be changed to mono-spaced. User under our project may need to add data for memory dumps etc.. Like the below comment
So the core is confirming just the two competing threads (as before):
(dbx) thread
thread state-k wchan state-u k-tid mode held scope function
$t1 run 0xf1000a00e027bb18 running 120586403 k no sys semop
*$t2 run running 73859303 k no sys _mutex_lock
$t3 run 0xf1000f0a1001d540 blocked 30736467 k no sys _event_sleep
>$t4 run 0x09001000a53efa90 blocked 35651829 k no sys _global_lock_common
$t5 run 0xf1000a00e027cd98 running 32571481 k no sys semop
$t6 run 0xf1000a00e027ce40 running 95748101 k no sys semop
$t7 run 0xf1000a00e027cb98 running 89522217 k no sys semop
$t8 run 0xf1000a00e027c418 running 64422015 k no sys semop
(dbx) thread current 4
warning: Thread is in kernel mode, not all registers can be accessed.
(dbx) where
_global_lock_common(??, ??, ??) at 0x90000000097d83c
_mutex_lock(??, ??, ??) at 0x90000000098b210
mFt_rt_savarea_step_start() at 0x90000002595c65c <- called pthread_mutex_lock
_mFginitdat() at 0x900000025a0c5f8
DSUB5010.init() at 0x900000002410abc
DSUB5010() at 0x9000000024106dc
SPCS0015_0x30a8() at 0x900000002416f30
SPCS0015() at 0x9000000024130d4
.sqloInvokeFnArgs.fdpr.chunk.1(??, ??, ??) at 0x9000000080a7948
sqloLatchCAS64.sqlerInvokeOLEUDF.fdpr.chunk.22(unsigned int,void**,sqleInvokerCB*)(??, ??) at 0x9000000080a7cc4
sqloLatchCAS64.sqlerInvokeOLEUDF.fdpr.chunk.10(unsigned int,void**,sqleInvokerCB*)(??, ??) at 0x900000007dd4474
sqlerFmpListener.fdpr.chunk.28(??, ??, ??, ??, ??) at 0x9000000080bcd1c
sqlerWorkerThreadEntry(void*)(??) at 0x9000000084dc860
0x09001000a53efa70 0000000300000000 0000000111072980 ..............).
0x09001000a53efa80 0000000000000000 0000000000000000 ................ ; pthread should start at 0x09001000a53efa88 based on wchan
0x09001000a53efa90 346700e700000000 0000000000000102 4g.............. ; wchan here
0x09001000a53efaa0 0000000000000000 0000000000000001 ................
0x09001000a53efab0 0000000000000004 000000000000009c ................
0x09001000a53efac0 0000000100000000 0000000000000000 ................
0x09001000a53efad0 09001000a53f4188 09001000a53f0a10 .....?A......?..
0x09001000a53efae0 0000000000000001 0000000000000000 ................
A locked pthread mutex (on AIX) has bits 27-0 of the 32-bit wchan value as the thread ID - so we can see this is thread ID 0x46700e7 = 73859303.