This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: Preparing for the GDB 5.0 / GDB 2000 / GDB2k release
- To: dan at cgsoftware dot com
- Subject: Re: Preparing for the GDB 5.0 / GDB 2000 / GDB2k release
- From: Mark Kettenis <kettenis at wins dot uva dot nl>
- Date: Tue, 8 Feb 2000 01:51:44 +0100
- CC: hjl at lucon dot org, gdb at sourceware dot cygnus dot com
- References: <Pine.LNX.4.10.10002071633590.9778-100000@propylaea.anduin.com>
Date: Mon, 7 Feb 2000 16:35:27 -0800 (PST)
From: Daniel Berlin <dan@cgsoftware.com>
> Debugging shared libraries works most of time with gdb 4.17.0.14.
> If it doesn't work with 5.0, does that count for serious losses of
> functionality? I believe many people will be very disappointed
> if it doesn't unless we can fix it within 2 months.
You mean for your particular architecture.
Please don't forget that.
Debugging shared libs works perfectly fine under BeOS, with my beos port,
using nothing but the standard solib hooks.
I bet debugging apps that dlopen() a shared object, then dlclose() it
and then dlopen() a different shared object won't work under BeOS
either (if that is possible under BeOS at all), but other than that,
I'm not aware of any deficiencies.
HJ, are you really aware of problems with debugging shared objects
that don't involve a dlclose() somehow? If you are, could you *please*
provide a testcase.
Mark