WebObjects 3.5.1: Additional gdb Troubleshooting

The WebObjects 3.5.1 release notes describe the following problem which may occur on Windows NT installations of WebObjects 3.5.1:

gdb breaks on unknown signal

Apple Reference #: 78366

Issue:

gdb breaks at the end of every request-response loop cycle, claiming that it has caught an unknown signal in closesocket.

Workaround:

Use the continue command to continue execution when gdb breaks. To prevent this from happening in the first place, do one of the following :

• Before running your application in gdb, enter the command set signal-exception 4.
• Create a gdb.ini file containing the set signal-exception command and save it in each of your .woa projects. You also can put it in your home directory to affect all projects that you work on.

In some cases, the solution described may not fully resolve the problem. In these cases, try the following additional step:

Under the Windows NT registry path:

HKEY_LOCAL_MACHINE\\SOFTWARE\\ORACLE

rename the key

OTRACE73

to (for example)

OTRACE73.RENAMED

This is an unsupported procedure and may create unknown side effects with the Oracle database. If problems occur, rename the key to its original name.