dbWorker3

Folks, IDS11.50 FC8, redHat Linux 6. Recently(after reverted) , dbWorker3 session ( see below) could dump/assert failed a couple of times daily..... Not very familiar to dbWorker3. Can we manage it ? Is it controllable ? Thanks, Frank [informix@stephanie tmp]$ more af.47b85224 01:11:00 Context ptr = 0x000000000178a480 01:11:00 Siginfo ptr = 0x000000000178a5b0 01:11:00 Reg 0(R8) 0x0000000000000000 Reg 1(R9) 0x0000000000000000 01:11:00 Reg 2(R10) 0x0000000000000008 Reg 3(R11) 0x0000000000000246 01:11:00 Reg 4(R12) 0x0000000045777570 Reg 5(R13) 0x00000000c6bae6f0 01:11:00 Reg 6(R14) 0x00000000c6bae6e0 Reg 7(R15) 0x00000000c6baec00 01:11:00 Reg 8(RDI) 0x00000000c6bae6e0 Reg 9(RSI) 0x00000000c6024028 01:11:00 Reg 10(RBP) 0x00000000c6bae6e0 Reg 11(RBX) 0x0000000000000001 01:11:00 Reg 12(RDX) 0x0000000000000000 Reg 13(RAX) 0x0000000000000000 01:11:00 Reg 14(RCX) 0x00007fd88445cba0 Reg 15(RSP) 0x00000000c6bae3e0 01:11:00 Reg 16(RIP) 0x000000000064bfe4 Reg 17(EFL) 0x0000000000010246 01:11:00 Reg 18(CSGSFS) 0x0000000000000033 Reg 19(ERR) 0x0000000000000004 01:11:00 Reg 20(TRAPNO) 0x000000000000000e Reg 21(OLDMASK) 0x0000000000000000 01:11:00 Reg 22(CR2) 0x0000000000000010 01:11:00 01:11:00 IBM Informix Dynamic Server Version 11.50.FC8 Software Serial Number AAA#B000000 01:11:00 Assert Failed: Exception Caught. Type: MT_EX_OS, Context: mem 01:11:00 Who: Session(13188, informix@, 0, 0xc238c5b8) Thread(17360, dbWorker3, c2376ae0, 1) File: mtex.c Line: 417 01:11:00 Action: Please notify IBM Informix Technical Support. 01:11:00 Raw hex dump of stack located in /tmp/af.47b85224.rawstk 01:11:00 Stack for thread: 17360 dbWorker3 base: 0x00000000c6b90000 len: 135168 pc: 0x00000000010c91d7 tos: 0x0000000001789590 state: running vp: 1 0x00000000010c91d7 (oninit) afstack 0x00000000010cb12c (oninit) afhandler 0x00000000010cb9e4 (oninit) affail_interface 0x00000000010cf7e9 (oninit) mt_ex_throw_sig 0x000000000108d895 (oninit) afsig_handler 0x00007fd8855b5500 (Linux) <signal frame> 0x000000000064bfe4 (oninit) sqapi_error_desc_first 0x000000000064e5c8 (oninit) sqapi_callback_list_call 0x000000000064eab8 (oninit) sqapi_call_callbacks 0x000000000064ca4c (oninit) sqapi_error_dispatch 0x000000000064d0e3 (oninit) sqapi_online_error 0x0000000000549e19 (oninit) mi_exec 0x0000000000d59383 (oninit) aus_refresh 0x0000000000968514 (oninit) udrlm_clang_execute_internal 0x000000000096a319 (oninit) udrlm_clang_execute 0x0000000000907846 (oninit) udrlm_exec_routine 0x000000000063e641 (oninit) udr_execute 0x0000000000559aa5 (oninit) mi_routine_exec 0x0000000000d507d9 (oninit) ph_exec_func 0x0000000000d55511 (oninit) ph_execute 0x0000000000d55be8 (oninit) do_task 0x0000000000d568a8 (oninit) db_sch_worker 0x000000000096861e (oninit) udrlm_clang_execute_internal 0x000000000096a319 (oninit) udrlm_clang_execute 0x0000000000907846 (oninit) udrlm_exec_routine 0x000000000063e641 (oninit) udr_execute 0x0000000000d4dda5 (oninit) dbsched_start_udr 0x000000000109a9bb (oninit) startup 01:11:00 See Also: /tmp/af.47b85224, shmem.47b85224.0 --------------------------------- Begin System Alarm Program Output --------------------------------- Assertion Failure Type: FAILURE Host Name: stephanie Database Server Name: nsofpal_tcp Time of failure: Sun Nov 24 01:11:00 UTC 2013 AF file: /tmp/af.47b85224 Shared memory file: None System Blocking: OFF ===========------------- - - - - - - tail -100 /dbbackup/online_log/online_pal.log: 01:00:09 Checkpoint Completed: duration was 0 seconds. 01:00:09 Sun Nov 24 - loguniq 89958, logpos 0x961d018, timestamp: 0x3027f49f Interval: 278316 01:00:09 Maximum server connections 93 01:00:09 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 80, Llog used 21 3 01:00:10 Level 0 Archive started on rootdbs, dblog1, dblog2, dberdata00, dbdata09_1, dbdata09_2, dbdata0 0, dbdata01, dbdata02, dbdata03, dbdata04, dbdata05, dbdata06, dbdata07, dbdata08, dbdata09, dbdata10, db data11, dbdw00, dbdw01, dbdw02, dbdw03, dbdw04, dbdw05, dbdw06, dbdw07, dbdw08, dbdata20, dbphylog, dbdat a12, dbdata13, dbdata21, dbersbdata00, dbersbdata01, dbsbdata00 01:05:23 Checkpoint Completed: duration was 0 seconds. 01:05:23 Sun Nov 24 - loguniq 89958, logpos 0x963b018, timestamp: 0x30281701 Interval: 278317 01:05:23 Maximum server connections 93 01:05:23 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 7, Llog used 30 01:07:52 listener-thread: err = -25582: oserr = 0: errstr = : Network connection is broken. 01:10:23 Checkpoint Completed: duration was 0 seconds. 01:10:23 Sun Nov 24 - loguniq 89958, logpos 0x968d018, timestamp: 0x302844be Interval: 278318 01:10:23 Maximum server connections 93 01:10:23 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 7, Llog used 82 01:11:00 Assert Failed: Exception Caught. Type: MT_EX_OS, Context: mem 01:11:00 IBM Informix Dynamic Server Version 11.50.FC8 01:11:00 Who: Session(13188, informix@, 0, 0xc238c5b8) Thread(17360, dbWorker3, c2376ae0, 1) File: mtex.c Line: 417 01:11:00 Action: Please notify IBM Informix Technical Support. 01:11:00 stack trace for pid 22737 written to /tmp/af.47b85224 01:11:00 See Also: /tmp/af.47b85224, shmem.47b85224.0 ===========------------- - - - - - - /usr/informix/bin/onstat -g ath: IBM Informix Dynamic Server Version 11.50.FC8 -- On-Line -- Up 3 days 09:23:53 -- 2870104 Kbytes Threads:tid tcb rstcb prty status vp-class name 2 c2e7f338 0 1 IO Idle 8lio* lio vp 0 3 c2ec22a8 0 1 IO Idle 9pio* pio vp 0 4 c2ee22a8 0 1 IO Idle 10aio* aio vp 0 5 c2f012a8 0 1 IO Idle 11msc* msc vp 0 6 c2f302a8 0 1 IO Idle 12fifo* fifo vp 0 7 c2f502a8 0 1 IO Idle 13aio* aio vp 1 8 c2f6f548 c2342028 3 sleeping secs: 1 1cpu main_loop() 9 c2ee2860 0 1 running 14soc* soctcppoll 10 c2f015c0 0 1 running 15soc* soctcppoll 11 c2f01970 0 1 sleeping forever 1cpu* sm_poll 12 c314c178 0 2 sleeping forever 1cpu* soctcplst 13 c31b1898 0 2 sleeping forever 1cpu sm_listen 14 c32a1028 0 1 sleeping secs: 1 1cpu sm_discon 15 c32f7220 0 2 sleeping forever 7cpu* soctcplst 16 c32f7a60 c2342880 1 sleeping secs: 1 1cpu flush_sub(0) 17 c32f7d78 c23430d8 1 sleeping secs: 1 1cpu flush_sub(1) 18 c33300e0 c2343930 1 sleeping secs: 1 1cpu flush_sub(2) 19 c33303f8 c2344188 1 sleeping secs: 1 1cpu flush_sub(3) 20 c3330710 c23449e0 1 sleeping secs: 1 1cpu flush_sub(4) 21 c3330a28 c2345238 1 sleeping secs: 1 1cpu flush_sub(5) 22 c3330d40 c2345a90 1 sleeping secs: 1 1cpu flush_sub(6) 23 c33c20e0 c23462e8 1 sleeping secs: 1 1cpu flush_sub(7) 24 c33c23f8 c2346b40 1 sleeping secs: 1 1cpu flush_sub(8) 25 c33c2710 c2347398 1 sleeping secs: 1 1cpu flush_sub(9) 26 c33c2a28 c2347bf0 1 sleeping secs: 1 1cpu flush_sub(10) 27 c33c2d40 c2348448 1 sleeping secs: 1 1cpu flush_sub(11) 28 c345e0e0 c2348ca0 1 sleeping secs: 1 1cpu flush_sub(12) 29 c345e3f8 c23494f8 1 sleeping secs: 1 1cpu flush_sub(13) 30 c345e710 c2349d50 1

Sysadmin thread and apart from disabling sysadmin I think you are stuck Cheers Paul Paul Watson Oninit www.oninit.com +1 913 387 7529 On Nov 23, 2013, at 20:00, "FRANK" <yunyaoqu@gmail.com> wrote: > Folks, > > IDS11.50 FC8, redHat Linux 6. > > Recently(after reverted) , dbWorker3 session ( see below) could > dump/assert failed a couple of times daily..... > > Not very familiar to dbWorker3. Can we manage it ? Is it controllable ? > > Thanks, > Frank > > [informix@stephanie tmp]$ more af.47b85224 > 01:11:00 Context ptr = 0x000000000178a480 > 01:11:00 Siginfo ptr = 0x000000000178a5b0 > 01:11:00 Reg 0(R8) 0x0000000000000000 Reg 1(R9) > 0x0000000000000000 > 01:11:00 Reg 2(R10) 0x0000000000000008 Reg 3(R11) > 0x0000000000000246 > 01:11:00 Reg 4(R12) 0x0000000045777570 Reg 5(R13) > 0x00000000c6bae6f0 > 01:11:00 Reg 6(R14) 0x00000000c6bae6e0 Reg 7(R15) > 0x00000000c6baec00 > 01:11:00 Reg 8(RDI) 0x00000000c6bae6e0 Reg 9(RSI) > 0x00000000c6024028 > 01:11:00 Reg 10(RBP) 0x00000000c6bae6e0 Reg 11(RBX) > 0x0000000000000001 > 01:11:00 Reg 12(RDX) 0x0000000000000000 Reg 13(RAX) > 0x0000000000000000 > 01:11:00 Reg 14(RCX) 0x00007fd88445cba0 Reg 15(RSP) > 0x00000000c6bae3e0 > 01:11:00 Reg 16(RIP) 0x000000000064bfe4 Reg 17(EFL) > 0x0000000000010246 > 01:11:00 Reg 18(CSGSFS) 0x0000000000000033 Reg 19(ERR) > 0x0000000000000004 > 01:11:00 Reg 20(TRAPNO) 0x000000000000000e Reg 21(OLDMASK) > 0x0000000000000000 > 01:11:00 Reg 22(CR2) 0x0000000000000010 > 01:11:00 > 01:11:00 IBM Informix Dynamic Server Version 11.50.FC8 Software Serial > Number AAA#B000000 > 01:11:00 Assert Failed: Exception Caught. Type: MT_EX_OS, Context: mem > 01:11:00 Who: Session(13188, informix@, 0, 0xc238c5b8) > > Thread(17360, dbWorker3, c2376ae0, 1) > > File: mtex.c Line: 417 > 01:11:00 Action: Please notify IBM Informix Technical Support. > 01:11:00 Raw hex dump of stack located in /tmp/af.47b85224.rawstk > 01:11:00 Stack for thread: 17360 dbWorker3 > base: 0x00000000c6b90000 > len: 135168 > > pc: 0x00000000010c91d7 > tos: 0x0000000001789590 > state: running > > vp: 1 > 0x00000000010c91d7 (oninit) afstack > 0x00000000010cb12c (oninit) afhandler > 0x00000000010cb9e4 (oninit) affail_interface > 0x00000000010cf7e9 (oninit) mt_ex_throw_sig > 0x000000000108d895 (oninit) afsig_handler > 0x00007fd8855b5500 (Linux) <signal frame> > 0x000000000064bfe4 (oninit) sqapi_error_desc_first > 0x000000000064e5c8 (oninit) sqapi_callback_list_call > 0x000000000064eab8 (oninit) sqapi_call_callbacks > 0x000000000064ca4c (oninit) sqapi_error_dispatch > 0x000000000064d0e3 (oninit) sqapi_online_error > 0x0000000000549e19 (oninit) mi_exec > 0x0000000000d59383 (oninit) aus_refresh > 0x0000000000968514 (oninit) udrlm_clang_execute_internal > 0x000000000096a319 (oninit) udrlm_clang_execute > 0x0000000000907846 (oninit) udrlm_exec_routine > 0x000000000063e641 (oninit) udr_execute > 0x0000000000559aa5 (oninit) mi_routine_exec > 0x0000000000d507d9 (oninit) ph_exec_func > 0x0000000000d55511 (oninit) ph_execute > 0x0000000000d55be8 (oninit) do_task > 0x0000000000d568a8 (oninit) db_sch_worker > 0x000000000096861e (oninit) udrlm_clang_execute_internal > 0x000000000096a319 (oninit) udrlm_clang_execute > 0x0000000000907846 (oninit) udrlm_exec_routine > 0x000000000063e641 (oninit) udr_execute > 0x0000000000d4dda5 (oninit) dbsched_start_udr > 0x000000000109a9bb (oninit) startup > > 01:11:00 See Also: /tmp/af.47b85224, shmem.47b85224.0 > --------------------------------- > Begin System Alarm Program Output > --------------------------------- > Assertion Failure Type: FAILURE > Host Name: stephanie > Database Server Name: nsofpal_tcp > Time of failure: Sun Nov 24 01:11:00 UTC 2013 > AF file: /tmp/af.47b85224 > Shared memory file: None > System Blocking: OFF > > ===========------------- - - - - - - > tail -100 /dbbackup/online_log/online_pal.log: > 01:00:09 Checkpoint Completed: duration was 0 seconds. > 01:00:09 Sun Nov 24 - loguniq 89958, logpos 0x961d018, timestamp: > 0x3027f49f Interval: 278316 > 01:00:09 Maximum server connections 93 > 01:00:09 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked > 0, Plog used 80, Llog used 21 > 3 > 01:00:10 Level 0 Archive started on rootdbs, dblog1, dblog2, dberdata00, > dbdata09_1, dbdata09_2, dbdata0 > 0, dbdata01, dbdata02, dbdata03, dbdata04, dbdata05, dbdata06, dbdata07, > dbdata08, dbdata09, dbdata10, db > data11, dbdw00, dbdw01, dbdw02, dbdw03, dbdw04, dbdw05, dbdw06, dbdw07, > dbdw08, dbdata20, dbphylog, dbdat > a12, dbdata13, dbdata21, dbersbdata00, dbersbdata01, dbsbdata00 > 01:05:23 Checkpoint Completed: duration was 0 seconds. > 01:05:23 Sun Nov 24 - loguniq 89958, logpos 0x963b018, timestamp: > 0x30281701 Interval: 278317 > 01:05:23 Maximum server connections 93 > 01:05:23 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked > 0, Plog used 7, Llog used 30 > 01:07:52 listener-thread: err = -25582: oserr = 0: errstr = : Network > connection is broken. > 01:10:23 Checkpoint Completed: duration was 0 seconds. > 01:10:23 Sun Nov 24 - loguniq 89958, logpos 0x968d018, timestamp: > 0x302844be Interval: 278318 > 01:10:23 Maximum server connections 93 > 01:10:23 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked > 0, Plog used 7, Llog used 82 > 01:11:00 Assert Failed: Exception Caught. Type: MT_EX_OS, Context: mem > 01:11:00 IBM Informix Dynamic Server Version 11.50.FC8 > 01:11:00 Who: Session(13188, informix@, 0, 0xc238c5b8) > > Thread(17360, dbWorker3, c2376ae0, 1) > > File: mtex.c Line: 417 > 01:11:00 Action: Please notify IBM Informix Technical Support. > 01:11:00 stack trace for pid 22737 written to /tmp/af.47b85224 > 01:11:00 See Also: /tmp/af.47b85224, shmem.47b85224.0 > > ===========------------- - - - - - - > /usr/informix/bin/onstat -g ath: > IBM Informix Dynamic Server Version 11.50.FC8 -- On-Line -- Up 3 days > 09:23:53 -- 2870104 Kbytes > Threads:> tid tcb rstcb prty status > vp-class name > 2 c2e7f338 0 1 IO Idle > 8lio* lio vp 0 > 3 c2ec22a8 0 1 IO Idle > 9pio* pio vp 0 > 4 c2ee22a8 0 1 IO Idle > 10aio* aio vp 0 > 5 c2f012a8 0 1 IO Idle > 11msc* msc vp 0 > 6 c2f302a8 0 1 IO Idle > 12fifo* fifo vp 0 > 7 c2f502a8 0 1 IO Idle > 13aio* aio vp 1 > 8 c2f6f548 c2342028 3 sleeping secs: 1 > 1cpu main_loop() > 9 c2ee2860 0 1 running > 14soc* soctcppoll > 10 c2f015c0 0 1 running > 15soc* soctcppoll > 11 c2f01970 0 1 sleeping forever > 1cpu* sm_poll > 12 c314c178 0 2 sleeping forever > 1cpu* soctcplst > 13 c31b1898 0 2 sleeping forever > 1cpu sm_listen > 14 c32a1028 0 1 sleeping secs: 1 > 1cpu sm_discon > 15 c32f7220 0 2 sleeping forever > 7cpu* soctcplst > 16 c32f7a60 c2342880 1 sleeping secs: 1 > 1cpu flush_sub(0) > 17 c32f7d78 c23430d8 1 sleeping secs: 1 > 1cpu flush_sub(1) > 18 c33300e0 c2343930 1 sleeping secs: 1 > 1cpu flush_sub(2) > 19 c33303f8 c2344188 1 sleeping secs: 1 > 1cpu flush_sub(3) > 20 c3330710 c23449e0 1 sleeping secs: 1 > 1cpu flush_sub(4) > 21 c3330a28 c2

Or disable the task Cheers Paul Paul Watson Oninit www.oninit.com +1 913 387 7529 On Nov 23, 2013, at 22:26, "Paul Watson" <paul@oninit.com> wrote: > Sysadmin thread and apart from disabling sysadmin I think you are stuck > > Cheers > Paul > > Paul Watson > Oninit www.oninit.com > +1 913 387 7529 > > On Nov 23, 2013, at 20:00, "FRANK" <yunyaoqu@gmail.com> wrote: > >> Folks, >> >> IDS11.50 FC8, redHat Linux 6. >> >> Recently(after reverted) , dbWorker3 session ( see below) could >> dump/assert failed a couple of times daily..... >> >> Not very familiar to dbWorker3. Can we manage it ? Is it controllable ? >> >> Thanks, >> Frank >> >> [informix@stephanie tmp]$ more af.47b85224 >> 01:11:00 Context ptr = 0x000000000178a480 >> 01:11:00 Siginfo ptr = 0x000000000178a5b0 >> 01:11:00 Reg 0(R8) 0x0000000000000000 Reg 1(R9) >> 0x0000000000000000 >> 01:11:00 Reg 2(R10) 0x0000000000000008 Reg 3(R11) >> 0x0000000000000246 >> 01:11:00 Reg 4(R12) 0x0000000045777570 Reg 5(R13) >> 0x00000000c6bae6f0 >> 01:11:00 Reg 6(R14) 0x00000000c6bae6e0 Reg 7(R15) >> 0x00000000c6baec00 >> 01:11:00 Reg 8(RDI) 0x00000000c6bae6e0 Reg 9(RSI) >> 0x00000000c6024028 >> 01:11:00 Reg 10(RBP) 0x00000000c6bae6e0 Reg 11(RBX) >> 0x0000000000000001 >> 01:11:00 Reg 12(RDX) 0x0000000000000000 Reg 13(RAX) >> 0x0000000000000000

Paul, What particular tasks to disable? Thanks, Frank On Sun, Nov 24, 2013 at 12:46 AM, Paul Watson <paul@oninit.com> wrote: > Or disable the task > > Cheers > Paul > > Paul Watson > Oninit www.oninit.com > +1 913 387 7529 > > On Nov 23, 2013, at 22:26, "Paul Watson" <paul@oninit.com> wrote: > > > Sysadmin thread and apart from disabling sysadmin I think you are stuck > > > > Cheers > > Paul > > > > Paul Watson > > Oninit www.oninit.com > > +1 913 387 7529 > > > > On Nov 23, 2013, at 20:00, "FRANK" <yunyaoqu@gmail.com> wrote: > > > >> Folks, > >> > >> IDS11.50 FC8, redHat Linux 6. > >> > >> Recently(after reverted) , dbWorker3 session ( see below) could > >> dump/assert failed a couple of times daily..... > >> > >> Not very familiar to dbWorker3. Can we manage it ? Is it controllable ? > >> > >> Thanks, > >> Frank > >> > >> [informix@stephanie tmp]$ more af.47b85224 > >> 01:11:00 Context ptr = 0x000000000178a480 > >> 01:11:00 Siginfo ptr = 0x000000000178a5b0 > >> 01:11:00 Reg 0(R8) 0x0000000000000000 Reg 1(R9) > >> 0x0000000000000000 > >> 01:11:00 Reg 2(R10) 0x0000000000000008 Reg 3(R11) > >> 0x0000000000000246 > >> 01:11:00 Reg 4(R12) 0x0000000045777570 Reg 5(R13) > >> 0x00000000c6bae6f0 > >> 01:11:00 Reg 6(R14) 0x00000000c6bae6e0 Reg 7(R15) > >> 0x00000000c6baec00 > >> 01:11:00 Reg 8(RDI) 0x00000000c6bae6e0 Reg 9(RSI) > >> 0x00000000c6024028 > >> 01:11:00 Reg 10(RBP) 0x00000000c6bae6e0 Reg 11(RBX) > >> 0x0000000000000001 > >> 01:11:00 Reg 12(RDX) 0x0000000000000000 Reg 13(RAX) > >> 0x0000000000000000 > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --089e013c5af02f2e5c04ec8ebdc3

Look at the stack trace for the thread, with luck you can see the task. If not then onmode -I <err> (err that is being thrown) and then look at the thread Cheers Paul > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of > FRANK > Sent: Monday, December 02, 2013 9:22 AM > To: ids@iiug.org > Subject: Re: dbWorker3 [32076] > > Paul, What particular tasks to disable? Thanks, Frank > > On Sun, Nov 24, 2013 at 12:46 AM, Paul Watson <paul@oninit.com> wrote: > > > Or disable the task > > > > Cheers > > Paul > > > > Paul Watson > > Oninit www.oninit.com > > +1 913 387 7529 > > > > On Nov 23, 2013, at 22:26, "Paul Watson" <paul@oninit.com> wrote: > > > > > Sysadmin thread and apart from disabling sysadmin I think you are stuck > > > > > > Cheers > > > Paul > > > > > > Paul Watson > > > Oninit www.oninit.com > > > +1 913 387 7529 > > > > > > On Nov 23, 2013, at 20:00, "FRANK" <yunyaoqu@gmail.com> wrote: > > > > > >> Folks, > > >> > > >> IDS11.50 FC8, redHat Linux 6. > > >> > > >> Recently(after reverted) , dbWorker3 session ( see below) could > > >> dump/assert failed a couple of times daily..... > > >> > > >> Not very familiar to dbWorker3. Can we manage it ? Is it controllable ? > > >> > > >> Thanks, > > >> Frank > > >> > > >> [informix@stephanie tmp]$ more af.47b85224 > > >> 01:11:00 Context ptr = 0x000000000178a480 > > >> 01:11:00 Siginfo ptr = 0x000000000178a5b0 > > >> 01:11:00 Reg 0(R8) 0x0000000000000000 Reg 1(R9) > > >> 0x0000000000000000 > > >> 01:11:00 Reg 2(R10) 0x0000000000000008 Reg 3(R11) > > >> 0x0000000000000246 > > >> 01:11:00 Reg 4(R12) 0x0000000045777570 Reg 5(R13) > > >> 0x00000000c6bae6f0 > > >> 01:11:00 Reg 6(R14) 0x00000000c6bae6e0 Reg 7(R15) > > >> 0x00000000c6baec00 > > >> 01:11:00 Reg 8(RDI) 0x00000000c6bae6e0 Reg 9(RSI) > > >> 0x00000000c6024028 > > >> 01:11:00 Reg 10(RBP) 0x00000000c6bae6e0 Reg 11(RBX) > > >> 0x0000000000000001 > > >> 01:11:00 Reg 12(RDX) 0x0000000000000000 Reg 13(RAX) > > >> 0x0000000000000000 > > > > > > > > > ********************************************************** > ********************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > > --089e013c5af02f2e5c04ec8ebdc3 > > > ********************************************************** > ********************* > Forum Note: Use "Reply" to post a response in the discussion forum.