Re: SET BREAK/CALL equiv. on gdb

[Eli Zaretskii]

> Date: Thu, 16 Sep 2004 11:36:02 -0400
> From: Michael Chastain <address@hidden>
> Cc: address@hidden,
>       address@hidden,
>       address@hidden
> 
> gdb needs "one source breakpoint -> multiple object breakpoints"
> for other reasons, specifically for c++ constructors and destructors.
> With that machinery, rbreak could set ONE source breakpoint and
> be much easier to manage.

I understood the "one source" part at face value: meaning, we are
setting a breakpoint on a single source line, which just happens to
have several translations in the machine code.  From that perspective,
using this feature for rbreak would be an abuse, I think, as rbreak
sets breakpoints on many source lines that have nothing in common
except the names of the functions.