bug#17893: 24.4.50; (error "Marker does not point anywhere")

[Charles A. Roelli]

> Bother: this is actually the tip of an iceberg.  Buffer local
> variables that get cloned by clone-buffer could hold any number of
> markers pointing into the original buffer.  E.g., info.el itself
> maintains a per-buffer marker in Info-tag-table-marker; evaluate it
> after M-n and see what it tells you.

> For mark-ring, I think it's easier to just reset it to nil in the new
> clone (it's arguably even more correct, since this is a fresh buffer),
> but in general this is a ticking bomb, unless I'm missing something.
> If I'm right, the only solution is to walk all the markers that point
> to the parent buffer and clone them to point to the cloned buffer
> (this has to be done in C).

By C, do you mean the function `clone-buffer'?