Windows
To help generate the Stack Trace Dump file on Windows platforms, another file must now be installed in the \bin directory along with arcmain.exe. This new file is arcmain.pdb.
In earlier versions of ARC on Windows platforms, an Access Violation error would generate the following output:
12/02/2010 09:55:25 *** Internal Failure ARC0001:UNEXPECTED
TERMINATION,REASON=ACCESS VIOLATION at address
00533412, accessing memory at 0053c636
12/02/2010 09:55:25 --- Disconnecting all sessions.
12/02/2010 09:55:25 LOGGED OFF 7 SESSIONS
================================================================
Execution traceback not available on this platform.
================================================================
12/02/2010 09:55:25 ARCMAIN TERMINATED WITH SEVERITY 16
If a Stack Trace Dump is generated, ARC will now display the following:
12/02/2010 09:55:25 *** Internal Failure ARC0001:UNEXPECTED
TERMINATION,REASON=ACCESS VIOLATION at address
00535292, accessing memory at 0053e636
12/02/2010 09:55:25 --- Disconnecting all sessions.
12/02/2010 09:55:25 LOGGED OFF 7 SESSIONS
================================================================
Stack trace dump file generated: Arcmain_Crash_2788.txt.
================================================================
12/02/2010 09:55:25 ARCMAIN TERMINATED WITH SEVERITY 16
If a Stack Trace Dump is not generated, ARC will now display the following:
12/02/2010 09:55:25 *** Internal Failure ARC0001:UNEXPECTED
TERMINATION,REASON=ACCESS VIOLATION at address
00533412, accessing memory at 0053c636
12/02/2010 09:55:25 --- Disconnecting all sessions.
12/02/2010 09:55:25 LOGGED OFF 7 SESSIONS
================================================================
Execution traceback not available.
================================================================
12/02/2010 09:55:25 ARCMAIN TERMINATED WITH SEVERITY 16
On Windows platforms, the contents of the Stack Trace Dump file (Arcmain_Crash_2788.txt) looks like the following:
Stack Dump file: Arcmain_Crash_2788.txt:
UNEXPECTED TERMINATION, REASON=ACCESS VIOLATION at address 00535292, accessing memory at 0053e636
Registers:
EAX:0053E636 EBX:7FFDE000 ECX:00000030 EDX:0053E65B
ESI:01CB9249 EDI:E1C5FAC4 EBP:0010C6F4 ESP:0010C44C Flags:00010206
CS:EIP:001B:00535292 DS:0023 ES:0023 FS:003B GS:0000 SS:0023
1: 00535292 UTXPrint+1F2 c:\...\utprint.c:230
2: 00483984 SetObjHasDataFlag+84 c:\...\dmpsvc1.c:777
3: 004823A4 GetTBIDs+1C4 c:\...\dmpsvc1.c:2084
4: 004810BC DMDICT+D6C c:\...\dmpsvc1.c:1758
5: 0050CC95 SHStHndl+415 c:\...\shsthndl.c:377
6: 004EB9FE DMPhase1+DE c:\...\shdump.c:1615
7: 0050CC95 SHStHndl+415 c:\...\shsthndl.c:377
8: 004EDDF0 DMObject+480 c:\...\shdump.c:2485
9: 004ECBC7 SHDump+627 c:\...\shdump.c:2991
10: 00475921 CTCMain+12F1 c:\...\ctcmain.c:1775
11: 0046CA15 main+2D5 c:\...\arcmain.c:195
12: 00539336 __tmainCRTStartup+1A6 f:\...\crtexe.c:586
13: 0053917D mainCRTStartup+D f:\...\crtexe.c:403
14: 7C817067 RegisterWaitForInputIdle+49 Unknown file
Each line in the Stack Dump file contains the following information:
1: 00535292 UTXPrint+1F2 c:\...\utprint.c:230
1) '1:' -- line item number
2) '00535292' -- memory address of last line executed in current
routine
3) 'UTXPrint+1F2' -- routine name plus memory offset into the routine
4) 'c:\...\utprint.c' -- full path of the module containing the routine
5) ':230' -- line offset within the module
Linux
In earlier versions of ARC on Linux platform, an illegal memory access error would generate the following output:
12/03/2010 11:42:48 *** Internal Failure ARC0001:OpsSHndl:An illegal
memory access was attempted
12/03/2010 11:42:48 LOGGED OFF 5 SESSIONS
================================================================
Execution traceback not available on this platform.
================================================================
12/03/2010 11:42:48 ARCMAIN TERMINATED WITH SEVERITY 16
If a Stack Trace Dump is generated, Teradata ARC displays the following:
12/03/2010 09:39:37 *** Internal Failure ARC0001:OpsSHndl:An illegal
memory access was attempted
12/03/2010 09:39:37 LOGGED OFF 5 SESSIONS
================================================================
Stack trace dump file generated: Arcmain_Crash_22434.txt.
================================================================
12/03/2010 09:39:37 ARCMAIN TERMINATED WITH SEVERITY 16
If a Stack Trace Dump is not generated, Teradata ARC displays the following:
12/03/2010 09:39:37 *** Internal Failure ARC0001:OpsSHndl:An illegal
memory access was attempted
12/03/2010 09:39:37 LOGGED OFF 5 SESSIONS
================================================================
Execution traceback not available.
================================================================
12/03/2010 09:39:37 ARCMAIN TERMINATED WITH SEVERITY 16
On Linux platforms, The contents of the Stack Trace Dump file (Arcmain_Crash_22434.txt) looks like the following:
Stack Dump file: Arcmain_Crash_22434.txt:
Signal Kind 11 [Segmentation fault]
Stack Trace:
[bt]: (1) /lib64/libc.so.6 [0x2aaaaabf6fc0]
[bt]: (2) arcmain(RstData+0xdd) [0x460b7d]
[bt]: (3) arcmain(MiniARC_RestoreTable+0x1d0) [0x426b20]
[bt]: (4) arcmain(MiniARC_GoRestore+0x250) [0x427120]
[bt]: (5) arcmain(SHMiniARC+0x532) [0x429762]
[bt]: (6) arcmain(CTCMain+0xfec) [0x40e87c]
[bt]: (7) arcmain(main+0x9) [0x40c3f9]
[bt]: (8) /lib64/libc.so.6(__libc_start_main+0xf4) [0x2aaaaabe4304]
[bt]: (9) arcmain(strcat+0x52) [0x40c34a]
Each line in the Stack Dump file contains the following information:
[bt]: (2) arcmain(RstData+0xdd) [0x460b7d]
1) '[bt]:' -- backtrace
2) '(2)' -- line item number
3) 'arcmain' -- name of the program
4) '(RstData+0xdd)' -- routine name plus memory offset into the
routine
5) '[0x460b7d]' -- memory address of last line executed in
current routine