Date: Sun, 12 Mar 2000 10:39:35 -0500
From: Gisli Ottarsson <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Resent-From: [EMAIL PROTECTED]
X-Mailing-List: <[EMAIL PROTECTED]> archive/latest/1988
X-Loop: [EMAIL PROTECTED]
Precedence: list
Resent-Sender: [EMAIL PROTECTED]
Content-Type: text/plain; charset=US-ASCII
Dear GDB team (and Mr. Psarogiannakopoulos):
I use gdb version 4.18 under Linux version 2.2.13 to debug a
commercial C++ program compiled with gcc version 2.95.1.
...
I have finally become convinced that the problem is related to my use
of shared libraries. To make a case for this, I have created two
executables, one using my standard scheme, the other built directly
from object files, skipping the intermediated shared libraries.
The breakpoint problem is a known problem in stock GDB 4.18 on Linux.
This will be fixed in the next release. You probably should use
whatever version of GDB comes with your Linux distribution. Or if
you like living dangerously, you might want to try a recent snapshot,
see http://sourceware.cygnus.com/gdb.
The problem with running out of memory is probably related to the
copious amount of debugging information generated by GCC for C++.
There has been a discussion on the GCC mailing list about this.
Apparently GDB cannot cope very well with all this information. On
the GDB web page, there is a link to the Mozilla debugging FAQ, that
provides some workarounds.
Mark
