From: David K. <da...@gi...> - 2004-06-06 04:18:59
|
Dan Aloni <da...@co...> wrote: > On Fri, Jun 04, 2004 at 03:04:11PM +0100, Yonghao Wang wrote: > > > daemon: loading configuration from colinux.default.xml > > > > and it popup a windows error message: > > > > "The instruction at "0x0040af85" referenced memory at "0x00000000". The > > memory could not be "read". > > It appears the crash was inside mxml_string_getc. It is possible that > the mxml library crashed on an invalid XML. Please send it over. > > -- > Dan Aloni > da...@co... hi Dan, i ran into this bug too. the first text editor i tried to use to edit the coLinux config file was UltraEdit32. this particular program feels that it's necessary to prepend a BOM (or Byte Order Mark) to the beginning of the file, just because it's "Unicode". coLinux crashes if the xml file starts with a BOM - perhaps it should be renamed a BOMB :-) anyway i suppose colinux needs to be taught to tolerate this thing since other editors do that as well -- apparently Notepad BOMbs xml files, too (see http://koti.mbnet.fi/akini/java/unicodereader/, http://lists.xml.org/archives/xml-dev/200106/msg00389.html and http://blogs.msdn.com/oldnewthing/archive/2004/03/24/95235.aspx). it pisses me off that my editor did that, silently without telling me, as it made my very first experience with coLinux a very frustrating one! it was not until i opened the BOM-munged file in a real *text* editor (rather than a wannabe Unicode editor) that i was warned that this supposed text file now contained binary (high ASCII) characters, and helped me avoid these nasty crashes. and Yonghao, if you need a text editor that doesn't screw up the colinux config file, check out MetaPad: http://liquidninja.com/metapad hope this helps! -dave |