#669 Eclipse: Perl EPIC debug & release mode execution mismatch

v0.6.x
closed-invalid
5
2015-02-19
2014-03-03
InnovWelt
No

The question that I asked on stackoverflow.com:

http://stackoverflow.com/questions/22152287/eclipse-perl-epic-debug-release-mode-execution-mismatch

There is a mismatch between debug & run mode executions of Eclipse Perl EPIC.

Consider the simple souce code files in attachment.

Here, the execution file "sample.pl" is shown below:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
#!/usr/bin/perl
# Code goes here ...
use strict;
use warnings;

use package1;

require "package1.pm";
require "package2.pm";

sampleFunction();

require "packagetest.pm";

packagetest::callSampleFunction();

If we execute this file in Debug mode, we get below console output:

from package2.pm
from package2.pm

If we execute this file in Run mode, we get below console output:

Subroutine sampleFunction redefined at D:/My.Soft.Dev/Perl_XS/package2.pm line 11.
from package1.pm
from package2.pm

Specifications:

Perl version: (v5.12.4) built for MSWin32-x86-multi-thread
Eclipse version: Indigo Service Release 2
EPIC version: 0.6.53, 0.6.54
OS: Windows 7

1 Attachments

Discussion

  • Jan Ploski

    Jan Ploski - 2014-03-03

    The same mismatch can be observed when running via command line with "perl -d" (perl 5.10.1, Linux), so the observed behavior is not due to EPIC. EPIC is just a debugger frontend. I guess you're hitting some perl debugger bug. perl 5.18.2 behaves as it should.

     
  • Jan Ploski

    Jan Ploski - 2014-03-03
    • status: open --> closed-invalid
    • assigned_to: Jan Ploski
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks