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: Mark Kettenis <kettenis at wins dot uva dot nl>
- Subject: Re: Preparing for the GDB 5.0 / GDB 2000 / GDB2k release
- From: Daniel Berlin <dan at cgsoftware dot com>
- Date: Mon, 7 Feb 2000 16:58:34 -0800 (PST)
- cc: hjl at lucon dot org, gdb at sourceware dot cygnus dot com
>
> 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.
No, they work fine.
You don't dlopen, you use load_add_on and unload_add_on, but it's
basically they same thing (you can emulate dlopen/dlclose perfectly with
it).
I just get notification of image (executable/shared library/etc)
createion/deletion from the debugger nub, and handle it there.
>
> 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
>
>