Re^2: Win32 - Memory can not be "read"

[HuckinFappy]

thanks for the translation. That's roughly in line with what I thought it was telling me. unfortunately, this is all very sporatic, so I'm not sure how to go about capturing a symbol dump.

I also don't see any stack dump in the System Event Viewer

This is perl 5.8.5 (I'll include perl -V at the end of this reply)

I don't have a specific code I'm suspicious of. I've see this happen apprently when my scripts are:

• Running make
• Using File::Find to gather find a collection of related files
• Running 'reg query' to get registry settings
• Spawning a variety of other system commands

Summary of my perl5 (revision 5 version 8 subversion 5) configuration:
  Platform:
    osname=MSWin32, osvers=4.0, archname=MSWin32-x86-multi-thread
    uname=''
    config_args='undef'
    hint=recommended, useposix=true, d_sigaction=undef
    usethreads=undef use5005threads=undef useithreads=define usemultip
+licity=define
    useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
    use64bitint=undef use64bitall=undef uselongdouble=undef
    usemymalloc=n, bincompat5005=undef
  Compiler:
    cc='cl', ccflags ='-nologo -Gf -W3 -MD -Zi -DNDEBUG -O1 -DWIN32 -D
+_CONSOLE -DNO_STRICT -DHAVE_DES_FCRYPT  -DPERL_IMPLICIT_CONTEXT -DPER
+L_IMPLICIT_SYS -DUSE_PERLIO -DPERL_MSVCRT_READFIX',
    optimize='-MD -Zi -DNDEBUG -O1',
    cppflags='-DWIN32'
    ccversion='', gccversion='', gccosandvers=''
    intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234
    d_longlong=undef, longlongsize=8, d_longdbl=define, longdblsize=10
    ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='__int64
+', lseeksize=8
    alignbytes=8, prototype=define
  Linker and Libraries:
    ld='link', ldflags ='-nologo -nodefaultlib -debug -opt:ref,icf  -l
+ibpath:"t:\perl\5.8.5\lib\CORE"  -machine:x86'
    libpth=\lib t:\perl\5.8.5\lib
    libs=  oldnames.lib kernel32.lib user32.lib gdi32.lib winspool.lib
+  comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib  netap
+i32.lib uuid.lib wsock32.lib mpr.lib winmm.lib  version.lib odbc32.li
+b odbccp32.lib msvcrt.lib
    perllibs=  oldnames.lib kernel32.lib user32.lib gdi32.lib winspool
+.lib  comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib  n
+etapi32.lib uuid.lib wsock32.lib mpr.lib winmm.lib  version.lib odbc3
+2.lib odbccp32.lib msvcrt.lib
    libc=msvcrt.lib, so=dll, useshrplib=yes, libperl=perl58.lib
    gnulibc_version='undef'
  Dynamic Linking:
    dlsrc=dl_win32.xs, dlext=dll, d_dlsymun=undef, ccdlflags=' '
    cccdlflags=' ', lddlflags='-dll -nologo -nodefaultlib -debug -opt:
+ref,icf  -libpath:"t:\perl\5.8.5\lib\CORE"  -machine:x86'


Characteristics of this binary (from libperl):
  Compile-time options: MULTIPLICITY USE_ITHREADS USE_LARGE_FILES PERL
+_IMPLICIT_CONTEXT PERL_IMPLICIT_SYS
  Built under MSWin32
  Compiled at Aug 12 2004 13:37:45
  @INC:
    c:/xgsPerl/5.8.5/lib
    c:/xgsPerl/site/5.8.5/lib
    c:/xgsPerl/site/lib
    .

[syphilis]

I'm not sure how to go about capturing a symbol dump

Does the pop-up you get have an option (button) that provides a dump ? I've a vague notion there's a "More Info" type button you can select, which produces the dump to a file ... but I'm not altogether sure.

Cheers,
Rob

[HuckinFappy]

You may be right, but we've hosed ourselves there.

Since these machines are used in gigantic overnight builds that run thousands of jobs each, we're turned off all popups. So there's an indicator in the Event Viewer that a popup would have been generated, but it doesn't actually show up. This prevents a pop-up waiting for a user response from causing the build to hang

I'll try and turn pop-ups back on selectively on our test network, and see if I can capture some more information

Thanks!

[GrandFather]

Have you tried updating your Perl?

[HuckinFappy]

I haven't tried upgrading. I can try that, but I have a couple of issues with that:
1. Perl is part of our engineering development environment. Since we're a month away from final release of our product, we're under an environment freeze, so an upgrade to perl is considered extremely disruptive
2. We'd been using the exact same version of perl, with the exact same code, for over a year with no issues, so I'm more interested in what may be causing this
That being said, I have a test network I can install a version of 5.8.8 on.

Thanks again

[GrandFather]

From point 2 I infer that the problem has started recently. If so, what else has changed in your environment? Windows updates perhaps? Other applications or drivers installed? New hard drives or other hardware?