Comment 1 for bug 205444

Here's what the bash manual says about readonly assignments:

> If any of the assignments attempts to assign a value to a
> readonly variable, an error occurs, and the command exits with a non-
> zero status.

So I guess that's the root cause of this problem. I would interpret this to mean that the script simply exits at this point, not merely turns off all debugging output.