I've got a module.pmod acting as a static class for some modules. In this class there is an error, but it didn't show up until I made another error in the same class (with newly added code)
This means I've been using _some_ version of my module.pmod other than I was expecting. This is very, very strange and frustrating.
Even more, when you take into account that I regularly start/stop roxen, using the startup script, killall ... and killall -9 ..., roxen is started with the --remove-dumped option, and the error even went by unnoticed after a full system (cold) reboot, which left the machine down for at least 48 hours.
Did pike or Roxen not notice the error or was the code not used at all?
Greetings,
Coen
__________________________________________________________ Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken.
The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system. __________________________________________________________