> Date: Fri, 1 Jan 2016 12:42:54 +0000 > From: Gavin Smith <[email protected]> > Cc: Texinfo <[email protected]> > > On 1 January 2016 at 11:08, Eli Zaretskii <[email protected]> wrote: > > Or maybe you have other ideas for possible reasons. (I don't have a > > debuggable version of Perl, so I cannot run it under a debugger to see > > where and why it fails, exactly.) > > Also if it dumps core, the backtrace could show where it crashed. That > could be meaningful, or could be completely unhelpful, it's hard to > know which.
There are no core dumps on Windows. If I tell Windows to attach a JIT debugger to Perl when it crashes, I get this information: perl.exe caused an Access Violation at location 7c83110c in module kernel32.dll Reading from location 01a4ffff. Registers: eax=00000000 ebx=00000008 ecx=01a4ffff edx=00000002 esi=00000000 edi=00000000 eip=7c83110c esp=0022f9a8 ebp=0022f9c0 iopl=0 nv up ei ng nz ac pe cy cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000293 Call stack: 7C83110C kernel32.dll:7C83110C FindActCtxSectionGuid 7C8310BA kernel32.dll:7C8310BA FindActCtxSectionGuid 7C831007 kernel32.dll:7C831007 FindActCtxSectionGuid 687435E2 XSParagraph.dll:687435E2 mbrtowc 687447A4 XSParagraph.dll:687447A4 xspara__add_next 6874483B XSParagraph.dll:6874483B xspara_add_next 68742722 XSParagraph.dll:68742722 XS_Texinfo__Convert__XSParagraph__XSParagraph_add_next My translation of the 1st line is that the code tried to read from an address that is outside the program's address space. Any ideas? There are several calls to mbrtowc in xspara__add_next. Btw, why is mbrtowc called with its 3rd argument 10? There are no such long multibyte sequences, AFAIK, and the value should IMO never be greater than the actual number of bytes in the variable whose address is passed as the 2nd arg. No?
