2004-02-17:The DEBUG defines have now been removed and currently only DEBUG_SERIAL exists.As it turned out, it didn't really make sense to support all that other stuffand only made the defintion uneccessary complex.A major change has been done with the configuration file and DEBUG output.Debugging:The debug statements are now printed with file, function and linenumberinformation, as well as with indentation to show the call tree. This makesdebugging much easier as it immedaitely points to where the message has beenissued. Also I created addtional functions which don't check the address ofmemory passed to it. With this you can issue debug messages also in placeswhere it was previously not possible because not everything was already initialized. You only have to take care that you don't use virtual memorywhen you call these functions. The new macro DVPRINT can do this.Configuration:The old handler for the configuration file has been removed. I ported ahandler to kernel mode wich I wrote to read/write MS Windows INI stylefiles. The new configuration file now looks like this:/etc/pice.conf ----------------= This is a comment# This is also a comment[Display]VideoDriver=vga[Init]SystemMap=/boot/System.map/etc/pice.conf ----------------For valid values of VideoDriver please look into config.c.I also created a macro which should fix the problem with a kernelfunction being changed from 2.4.18 to 2.4.19. Now pICE should compileon any kernel from 2.4.18 on.2003-06-18:Changed the behaviour of the DEBUG defines.Now you either have to define DEBUG (whichgoes to printk) or DEBUG_SERIAL (which goesof course to the serial port). If you need tocheck in the code if debugging should be activatedyou must use __PICE_DEBUG__ which is definedby both DEBUG symbols.2003-06-14:Added a new DEBUG define DEBUG_SERIAL. If presentthe output goes to the serial port. This was thedefault output previously. Now the normal DEBUGuses printk for debug logging.If you want to have debugging to serial you needto define both defines.