> Date: Fri, 1 Jan 2016 15:29:12 +0000 > From: Gavin Smith <[email protected]> > Cc: Texinfo <[email protected]> > > BTW this strikes me as strange: > > Reading from location 01a4ffff > > The ffff would make sense if memory protection was done in blocks of > 10000 (hex), and here we've strayed into a protected part of memory. > But I expect it would be more likely to read bytes in increasing > order, meaning we'd stray into xxx0000. If changing the argument to > mbrtowc fixes the problem, we needn't worry about it.
Strange indeed. Btw, in case it wasn't clear: the mbrtowc that's used here is the one from Gnulib, not from the MS-Windows runtime. According to disassembly of gnulib/lib/mbrtowc.o, it's the rpl_mbrtowc variant (near the end of the file) that's used in my case.
