+ we can transition to the new version of gdb completely. See below.
+
+/usr/gnu/bin/gdb:
+ This is the gdb from the ports area (if installed), also known as
+ gdb-4.11. There is a problem using gdb-4.11 to debug a core-file
+ generated by a binary which uses shared libraries. The problem is
+ basically due to the fact that the shared libraries are mmap'ed at
+ addresses in the memory space of the binary which are not accessible
+ to gdb-4.11 at the time that it tries to examine the core-file. This
+ usually manifests itself in "Cannot access memory at address <foo>"
+ messages at startup and "#0 <bar> in end ()" when you try to do
+ a backtrace ("bt").
+
+ Workaround: start gdb-4.11 without reference to the core-file,
+ e.g. "gdb fubar". Set a breakpoint in main and run the inferior
+ so that gdb-4.11 can resolve references to the shared libraries.
+ After this, use the "core-file" command to force gdb-4.11 to
+ load the core-file, e.g. "core-file fubar.core". Since all
+ shared library references were previously resolved gdb-4.11 can
+ now access the shared libraries and things like "bt" now work.
+ You will also be able to reference items previously on the stack
+ (from the core file), but all globals will show up as zero'd.
+ All these problems may be avoided if you compile the application
+ with -static.