You may receive a SIGBUS error (Signal 10 - Bus error) when you
run the COBOL DB2 API sample programs with no embedded SQL on
Solaris and HP-UX.
When trying to run the COBOL sample programs after building with
no error, you will see an error message like the following:
$ ./d_dbconf
Sample COBOL Program : D_DBCONF.CBL
Execution error : file 'd_dbconf'
error code: 114, pc=0, call=1, seg=0
114 Attempt to access item beyond bounds of memory (Signal
10)
You will see a stack trace similar to the following when using a
debugger:
=>[1] SMemBasePool::SMemBasePool(0xfc7a01e4, 0xcc, 0x7,
0xaaa00c00, 0xffff, 0xfc7a0068), at 0xfe1ebc58
[2] sqloCreateMemoryPool(0xfe6ce004, 0xfc7a01e4, 0x80000000,
0xfc7a0000, 0x0, 0x1), at 0xfe1d628c
[3] sqloGetPrivateSet(0xfc7a0000, 0x0, 0xff139a80, 0x0,
0xff1357b0, 0x0), at 0xfe1e2e84
[4] MemOssPool(0xffbff4a8, 0x0, 0xfe6ce004, 0xfe3e9bf8,
0xddf0, 0xdc00), at 0xfe1e19a0
[5] sqlogmblkEx(0xdb22fff8, 0xfe28fc78, 0x0, 0x1c080000,
0xdb22fff8, 0xac), at 0xfe1d92a8
[6] sqlo_init_generic_data(0xfeeea584, 0x9800, 0x710,
0xfe3e9bf8, 0xfeeea5bc, 0xfe5b9268), at 0xfdf65548
[7] sqlo_create_init_app_data(0xe8215, 0xfeeea584, 0x4558c,
0xfe5c1e72, 0xfe5c24a4, 0x0), at 0xfdf6cf10
[8] sqlgddb(0x6, 0x5, 0x38a30, 0x38830, 0x38a58, 0x38919), at
0xfdec0f90
[9] d_dbconf(0x42b60, 0x0, 0x20, 0x0, 0xff3f5110, 0x0), at
0x10d3c
[10] 0xfd796f18(0x10b80, 0x0, 0xffbffa54, 0x4, 0xffbff9d0,
0x42b60), at 0xfd796f18
[11] _mFgmain2(0xfd7a88e8, 0x1400, 0x10e0, 0x1, 0xffff0000,
0xfd7b65c4), at 0xfd776c80
[12] main(0x1, 0xffbffb24, 0xffbffb2c, 0x21800, 0xfc8c07c0,
0xfc820000), at 0x10b70 |
You may receive a SIGBUS error (Signal 10 - Bus error) when you
run the COBOL DB2 API sample programs with no embedded SQL on
Solaris and HP-UX.
When trying to run the COBOL sample programs after building with
no error, you will see an error message like the following:
$ ./d_dbconf
Sample COBOL Program : D_DBCONF.CBL
Execution error : file 'd_dbconf'
error code: 114, pc=0, call=1, seg=0
114 Attempt to access item beyond bounds of memory (Signal
10)
You will see a stack trace similar to the following when using a
debugger:
=>[1] SMemBasePool::SMemBasePool(0xfc7a01e4, 0xcc, 0x7,
0xaaa00c00, 0xffff, 0xfc7a0068), at 0xfe1ebc58
[2] sqloCreateMemoryPool(0xfe6ce004, 0xfc7a01e4, 0x80000000,
0xfc7a0000, 0x0, 0x1), at 0xfe1d628c
[3] sqloGetPrivateSet(0xfc7a0000, 0x0, 0xff139a80, 0x0,
0xff1357b0, 0x0), at 0xfe1e2e84
[4] MemOssPool(0xffbff4a8, 0x0, 0xfe6ce004, 0xfe3e9bf8,
0xddf0, 0xdc00), at 0xfe1e19a0
[5] sqlogmblkEx(0xdb22fff8, 0xfe28fc78, 0x0, 0x1c080000,
0xdb22fff8, 0xac), at 0xfe1d92a8
[6] sqlo_init_generic_data(0xfeeea584, 0x9800, 0x710,
0xfe3e9bf8, 0xfeeea5bc, 0xfe5b9268), at 0xfdf65548
[7] sqlo_create_init_app_data(0xe8215, 0xfeeea584, 0x4558c,
0xfe5c1e72, 0xfe5c24a4, 0x0), at 0xfdf6cf10
[8] sqlgddb(0x6, 0x5, 0x38a30, 0x38830, 0x38a58, 0x38919), at
0xfdec0f90
[9] d_dbconf(0x42b60, 0x0, 0x20, 0x0, 0xff3f5110, 0x0), at
0x10d3c
[10] 0xfd796f18(0x10b80, 0x0, 0xffbffa54, 0x4, 0xffbff9d0,
0x42b60), at 0xfd796f18
[11] _mFgmain2(0xfd7a88e8, 0x1400, 0x10e0, 0x1, 0xffff0000,
0xfd7b65c4), at 0xfd776c80
[12] main(0x1, 0xffbffb24, 0xffbffb2c, 0x21800, 0xfc8c07c0,
0xfc820000), at 0x10b70 |
