Re: Re: Problems with Win32::OLE and Excel specifically memory could not read/written.

I had not tried Devel::Trace, running that now I have found that in the last 3 times running/crashing it stopped at 3 different places in the code. The last on stopped at:
@contents = @$contentsref;

nothing wrong with that line, or any of the others that I have seen....

Yes I have VS Debug....running it by hitting 'cancel' gives me:
"Unhandled exception in perl.exe (NTDLL.DLL): 0xC0000005: Access Violation."

Further inspection shows:
NTDLL! 77fcb3af()    ->  77FCB3AF   mov         dword ptr eax+4,ecx
NTDLL! 77fcc8d7()    ->  77FCC8D7   mov         esi,eax
MSVCRT! 78001e00()   ->  78001E00   mov         ecx,dword ptr ebp-10h
PERL58! 280869f9()   ->  280869F9   mov         eax,dword ptr edi
PERL58! 28066179()   ->  28066179   cmp         dword ptr esi+4,0
PERL58! 28024dd7()   ->  28024DD7   add         esp,0Ch
GUI!01d90ec7()       ->  01D90EC7   add         esp,4
USER32! 77e3a2d0()   ->  77E3A2D0   cmp         dword ptr esp+4,0DCBAABCDh
USER32! 77e16362()   ->  77E16362   mov         ecx,eax
USER32! 77e17341()   ->  77E17341   jmp         77E17389
USER32! 77e308f5()   ->  77E308F5   ret         8
USER32! 77e2e00c()   ->  77E2E00C   jmp         77E2E01D
USER32! 77e3a2d0()   ->  77E3A2D0   cmp         dword ptr esp+4,0DCBAABCDh
USER32! 77e145e5()   ->  77E145E5   mov         ecx,eax
USER32! 77e15b51()   ->  77E15B51   ret         4
PERL58! 28040681()   ->  28040681   cmp         dword ptr ebp-10h,0
PERL58! 2805eda5()   ->  2805EDA5   test         eax,eax
PERL58! 28089764()   ->  28089764   pop         ecx
PERL! 00401012()     ->  00401012   add         esp,0Ch
KERNEL32! 7c5987e7() ->  7C5987E7   push         eax

I hope this means something to someone out there, cause my assembly knowledge is next to none.
The above code was taken from "context" in the debugger.

As far as file numbers being a factor...yes definately I know that the more files that I am converting the greater the chance of seeing this error....I think that it is statistical and not the cause. I have seen it fault @ 5% completion and at 75% completion, so the problem does occur at different file numbers.

I hope that this info can shed some light on this...if anyone else has any suggestions or needs any other info just say it...I will try nearly anything :)

Thanks again,

Cameron

Comment on Re: Re: Problems with Win32::OLE and Excel specifically memory could not read/written.

Replies are listed 'Best First'.
Re: Re: Re: Problems with Win32::OLE and Excel specifically memory could not read/written. by Grygonos (Chaplain) on Feb 25, 2004 at 21:51 UTC
Find which files it is faulting on. Analyze those files for any trends in the data. Perhaps certain data causes the violation in conjuction with your algorithm. Is it dying on files with extremely large numbers? Posting your full code will help give a better picture of what is going on. Perhaps it doesn't stop on the line that is at fault, but rather once perl has caught up with itself, it stops at whatever line it happens to be parsing at the time? Thinking aloud really.. some of the above is probably total bs. Just trying to foster ideas to help you with this. Grygonos	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Problems with Win32::OLE and Excel specifically memory could not read/written.
by Grygonos (Chaplain) on Feb 25, 2004 at 21:51 UTC

Find which files it is faulting on. Analyze those files for any trends in the data. Perhaps certain data causes the violation in conjuction with your algorithm. Is it dying on files with extremely large numbers? Posting your full code will help give a better picture of what is going on. Perhaps it doesn't stop on the line that is at fault, but rather once perl has caught up with itself, it stops at whatever line it happens to be parsing at the time?

Grygonos

[reply]