Hi,

Attached is a patch I have constructed against GDB 6.6 which adds the
following commands to GDB:

* disable sharedlibrary

  This command removes the shared library breakpoints and implicitly
calls the "nosharedlibrary" command. The solib_create_inferior_hook()
API is also disabled (until re-enabled by "enable sharedlibrary").

* enable sharedlibrary

  This command explicitly calls the solib_create_inferior_hook() API and
re-enables the auto loading of shared libraries.

The intent of this patch is to be able to control the insertion of the
breakpoint used to monitor when a shared library is loaded (and so
update GDB's symbolic information). The reason for this is that when
debugging boot from ROM applications it is only legitimate to insert a
breakpoint when the application has been re-located from ROM to RAM. At
present it is only possible to control this by removing the symbolic
information (so that GDB does not "see" the special symbol in the target
application). This is not desirable if one wishes to set a breakpoint
(using a hardware breakpoint) in the loaded application.

I plan to add these commands to the version of GDB we support, unless
someone suggests a better solution, but I would also like to get a wider
opinion (other than my own) on the implementation and whether the
changes a desirable in standard GDB.

Cheers,

Antony.