Re: blink-cursor-end sometimes fails and disrupts pre-command-hook

[Richard Stallman]

    "put them" == put the `(backtrace)' call
    "where" == at the point in the code for which you want the backtrace.

To put in an explicit call to (backtrace) is an unusual technique, but
I don't see why it would not work.  Since it outputs to
standard-output, you could save multiple backtraces in one buffer.

    what i want, instead, is the ability to get a stack trace for an error
    when i am handling that error, in a condition-case or in the
    interactive interpreter.

Does (setq debug-on-signal t) do what you want?
If not, precisely how does what you want differ from that?