| Language/OS Required | Release Date | Version | Read Me | Software |
|
Any language (multi-country)
Mac OS X Server |
2000-11-10 | 1.0 |
English |
30 K |
|
Any language (multi-country)
Windows NT or Windows 2000 |
2000-11-10 | 1.0 |
English |
40 K |
|
Any language (multi-country)
Solaris OS |
2000-11-10 | 1.0 |
English |
47 K |
|
Hardware Requirements |
|
|
Software Requirements |
|
|
|
|
|
Earlier versions of this software may be available at http://download.info.apple.com/ For help with downloading, see article 75098 " Help: Downloading Software "All software available from this site is covered by a software license agreement included with this software. |
|
Overview
When using the gdb debugger on programs built with WebObjects 4.0.1, or 4.5 on certain platforms (see "Products affected" below), the print-object command (usually abbreviated "po") sometimes produces extraneous output and sometimes prints unintelligible text instead of the object's description. A patch, described below, can fix this issue.
Symptom
When you use the print-object ("po") command, gdb may:
- Repeatedly print messages about "...autoreleased with no pool in place - just leaking." (Apple reference 2283470)
- Print unintelligible text, instead of the object's description. (Apple reference 2452071)
- Cause various errors from gdb, such as being unable to read memory. (Apple reference 2452071)
Products affected
- WebObjects 4.0.1 on Windows NT and Solaris
- WebObjects 4.5 on Windows NT and Solaris
- WebObjects 4.5 on Windows 2000 with WO 4.5 Update 2 or 3 installed
- WebObjects 4.5 on Mac OS X Server with WO 4.5 Update 2 or 3 installed
Solution
1. Download the tar archive containing the fix:
-
For Windows NT or Windows 2000, download GDBFixes_NT.tar (Notes 3 and 4))
-
For Solaris, download GDBFixes_Solaris.tar (Note 3)
- For Mac OS X Server, download GDBFixes_OSXS.tar (Note 3)
2. Unpack the .tar file
3. Follow the instructions in the READ ME file with the .tar archive on how to add the patch to a project on your platform.
Note: Each application you want to debug must have the patch installed; it does not update anything system-wide.
You may want to add commands to your gdb.ini file (on Windows) or .gdbinit file (on other systems) to set a breakpoint on a startup function and automatically install the fix. For example, your gdb.ini or .gdbinit file might include the following, which will take a few seconds to automatically do all the work for you:
b myStartup # change this to some startup function or method
commands
call fixGdbPrintObject()
continue
end
Another approach would be to use a command-line flag such as "-RunningGDB YES", and have your application check for this flag (using the NSUserDefaults class) and call fixGdbPrintObject() when the flag is true.
Notes:
- [NSObject autorelease] override adding autorelease pool to thread...
1. If you call fixGdbPrintObject(), you may later see diagnostic messages like the following. You can ignore them:
2. Do not call the fixGdbPrintObject() when your application is in production (unless you're trying to debug an issue in production). The extra checks it makes can significantly affect performance.
3. The gdb patch is intended for use with WebObjects applications, rather than AppKit applications.
4. When debugging AppKit applications on Windows NT and Windows 2000, the gdb patch may cause issues in the Open and Save panels. Some entries in the combo box for file types may be missing or damaged. To work around this, type the file type instead of selecting it from the menu.