On Thursday 12 February 2009 23:17:44 Daniel Jacobowitz wrote:
> On Thu, Feb 12, 2009 at 11:11:04PM +0300, Vladimir Prus wrote:
> > Can you write down the comment that disable_breakpoints_in_unloaded_shlib
> > would have to contain to explain all this? ;-) I assume it will go like this:
> > 
> > 	Don't emit any message here for a.out, because for all the other
> > 	targets some other code calls some other function that arranges for
> > 	this message to not be printed when rerunning the program...
> > 
> > In other words, the problem with checking for a.out is that it deeply depends on
> > intricate details of some other code.
> 
> It's not about the message, but about the disabling.  I mean:
> 
>   /* SunOS a.out shared libraries are always mapped, so do not
>      disable breakpoints; they will only be reported as unloaded
>      through clear_solib when GDB discards its shared library
>      list.  See clear_solib for more information.  */

For avoidance of doubt, is the attached OK code-wize?

- Volodya