It would be very useful for breakpoints to OPTIONALLY trigger even
when the script wasn't in debug mode. That's the easiest way to debug
a call that comes from "outside" (e.g. via a Web framework or XML RPC)
or where it's difficult to find the right starting point (e.g. some of the
more complex built-in behavior).
I suspect the right UI is to provide a global switch, e.g.
user.prefs.absoluteBreakpoints = false (the default).
Note that it's fine with me if setting to true slows "everything" down
(since all scripts would run in debug mode); it's an advanced feature to
use on occasion to figure out what's going on. And, in many cases,
isolate a sufficient starting point for a manual debug/follow.
As an alternative, one could attempt to isolate this to a specific script
or table, though I'm not sure sufficient information on the callers
would be available -- and that's part of the point.