Really? I don't see why they would make the VDR to crash - the plugin should just try to retune the channel after 5 seconds. I'd like to see syslog entries during the malfunction.
I was seeing that sessionM was undefined in case of 404 errors and thus the following code (from tuner.c, line 245 in vers 0.3.2)
crashes vdr, as the startswith function tries to access memory through an undefined pointer. But I have to admit that I have to reproduce this with version 0.3.2 (I definitely was seeing the crash with 0.3.1).
But: I really would prefer to have vdr exiting if we do get repeatedly 404 errors. Going in an indefinite retune loop would not help in this (very rare and probably not for a lot of people relevant) case. If vdr ends (preferrable with an error state), I can do the reboot of the DSI400 in the runvdr script and restart vdr and things will start working again.
And again: For me this is a rare case and needs usage of the DSI400 with multiple vdr instances and some hard crashes. It is not easy to reproduce. I will see if I can catch one of the crashes to further investigate.