|CC:||bug-PadWalker [...] rt.cpan.org|
|Subject:||Problem with EPIC debugger and Win32::OLE|
|Date:||Thu, 21 Feb 2008 12:45:19 +0100|
|To:||bug-libwin32 [...] rt.cpan.org|
|From:||Oliver.Koch [...] Linde-LE.com|
Dear all, I've found a problem with the debugger of EPIC. When stepping over the Win32::OLE code of my little demo script (instead of using Run or Resume), the program output from Win32::OLE is different (and wrong). (See attached file: OLE-Excel_EPIC_Debug_Error.pl) For details of my configuration and outputs please look into the demo script. In the beginning I suspected the error is related to the Padwalker module, because you can avoid the wrong output by disabling the "Show local variables" option of the variables view in EPIC. But I already had some debug attempts with Robin Houston, who admirably tried to check whether the padwalker module needs a fixed. Please, follow this thread for details:Finally, it seems to me that the problem is more related to Win32::OLE and/or EPIC. Perhaps, you'd analyze the problem based on your background. Regards, Oliver P.S.: I post this report to the EPIC team, too.
Message body is not shown because sender requested not to inline it.