This is the mail archive of the gdb@sourceware.cygnus.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Preparing for the GDB 5.0 / GDB 2000 / GDB2k release


On Mon, Feb 07, 2000 at 09:08:51AM -0800, Jim Kingdon wrote:
> > * Support for unloading of shared libraries.  The current code-base
> >   doesn't really support this.  HJ Lu forwarded some patches that hack
> >   around this, but I don't think they are acceptable.  They introduce
> >   two more (uneccessary) hooks.  Personally I don't fixing this for
> >   GDB 5.0 terribly important.  There isn't that many code out there, that
> >   explicitly unloads shared libs.
> 
> As far as I know there is more out there than you might realize.  A
> modern application like mozilla uses dlopen() a lot (feel free to
> flame about whether this tendency is a fad or really useful but that
> isn't the point).  For example see
> http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=5130
> 
> 
> > I think having an "x86 linux native" port with working threads support
> > in GDB 5.0 is very important.
> 
> Have you tried GDB from CVS in the last 6 months or so?  I'm not aware
> of any known bugs and Red Hat Linux has been shipping with the code
> which is in CVS for a while (I can offer details if needed).
> 

gdb 4.17.0.14 has one patch from Sam to deal with shared libraries.
People who want to debug shared libraries may not want to use gdb
in CVS. As you have mentioned above, it is not that unusual nowdays.
We have patches and they seem to work. We can make gdb 5.0 to work
with shared libraries. If we continue ignoring the working patches
without providing an alternative, we are sending the wrong signals
to those contributors.


H.J.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]