Skip Menu |

This queue is for tickets about the PadWalker CPAN distribution.

Report information
The Basics
Id: 33484
Status: new
Priority: 0/
Queue: PadWalker
People
Owner: Nobody in particular
Requestors: Oliver.Koch [...] Linde-LE.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Thu Feb 21 06:45:55 2008 Oliver.Koch [...] Linde-LE.com - Ticket created
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: http://rt.cpan.org/Ticket/Display.html?id=33211 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.

  Tue Mar 10 03:05:04 2009 Oliver.Koch [...] Linde-LE.com - Correspondence added
Subject: Re: [rt.cpan.org #33484] Problem with EPIC debugger and Win32::OLE
Date: Tue, 10 Mar 2009 08:04:51 +0100
To: bug-PadWalker [...] rt.cpan.org
From: Oliver.Koch [...] Linde-LE.com
*** e-mail to Jan Dubois, cc to Jan Ploski and Robin Houston *** Dear Jan, Thanks for the analysis. In general the explanation sounds reasonable. But to be honest I'm a little bit confused, because there is now a contradictory situation. From Padwalker module's point of view there couldn't be found a problem, from EPIC's point of view the problem is located in Win32::OLE, and from your's point of view the problem is within the debugger. Since I have not a deep enough insight into any of the three products, I feel, that I'm not capable to resolve this conflict. At first I'd like to ask, whether all parties have tested the same aspect of this incident? Secondly, I think, that the fastest and the most reliable way to fix this is, that you developers resolve this contradiction in direct communication: Jan Dubios <bug-Win32-OLE at rt.cpan.org> [rt.cpan.org #33485] Problem with EPIC debugger and Win32::OLE https://rt.cpan.org/Ticket/Display.html?id=33485 Jan Ploski <jpl at plosquare.com> [ 1898659 ] Problem with EPIC debugger and Win32::OLE http://sourceforge.net/tracker/index.php?func=detail&aid=1898659&group_id=75859&atid=545274 Robin Houston <bug-PadWalker at rt.cpan.org> [rt.cpan.org #33484] Problem with EPIC debugger and Win32::OLE http://rt.cpan.org/Ticket/Display.html?id=33484 [rt.cpan.org #33211] Problem with Eclipse EPIC and 'Show Local Variables' http://rt.cpan.org/Ticket/Display.html?id=33211 I hope, that this bring foward this incident to resolve without remaining questions. Kind regards, Oliver P.S.: I post this e-mail to all four treads.