The patch referred to in comment #6 should not be removed from gdb. When the pc is zero, gdb is in essence missing debug information and may be lost. In most instances, attempting to backtrace past such a point results in garbage traces that may not have an end condition (i.e. infinite backtraces). To alleviate the problem specified here, a new set backtrace sub-command has been added which gives the user the option of forcing a trace past a zero pc value. To use it: set backtrace past-zero-pc on By default, the option will be off. The option can be later set off via: set backtrace past-zero-pc off The sub-command has been added as of gdb-6.3.0.0-1.91
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2006-0106.html