|
Problem IC72591
|
Status: Closed |
WHEN ATTACHING DEBUGGER TO THE DB2SYSCS PROCESS, DB2SYSCS CRASHES WITH STACK OVERFLOW. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When attaching a Windows debugger (e.g. ADPlus, Windbg ) to the
db2syscs process, the db2syscs process crashes in the debugger
thread with STACK OVERFLOW exception.
This happens to x64 versions of v97GA, v97fp1, v97fp2 and
v97fp3.
This does not happen to x86 32 bit versions of DB2. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 for X64 Windows *
****************************************************************
* PROBLEM DESCRIPTION: *
* When attaching a Windows debugger (e.g. ADPlus, Windbg ) to *
* the *
* db2syscs process, the db2syscs process crashes in the *
* debugger *
* thread with STACK OVERFLOW exception. *
****************************************************************
* RECOMMENDATION: *
* Apply v97fp4 *
**************************************************************** |
| Local Fix: |
No workaround.
Do not use the debugger to attach to the db2syscs.exe for these
versions of DB2. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
This problem was first fixed in v97fp4 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC72647
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.11.2010
28.04.2011
28.04.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
