Allow killing indirect when base buffer has already been killed.

An unrelated activity killed a base buffer in a way that left its indirect buffer hanging around, and when I tried to kill off the indirect buffer manually I was blocked by an error in this hook function. (`with-current-buffer` complains when trying to activate a killed buffer) So here's a quick patch to guard against that issue.