EGL Development User Group

EGL Development User Group

EGL Development User Group

The EGL Development User Group is dedicated to sharing news, knowledge, and insights regarding the EGL language and Business Developer product. Consisting of IBMers, HCL, and users, this community collaborates to advance the EGL ecosystem.

 View Only
Expand all | Collapse all

EGL debugging problem

  • 1.  EGL debugging problem

    Posted Tue March 22, 2016 08:06 AM

    Hi,

    I'm trying debug a EGL program QA001P that call program BA001P.

    QA001P and BA001P are in diffents EGL Project and Package.

    When the program BA001P is called:

    call "BA001P"(BA001RW2){IsExternal = no};

    I received the following error message,

     

    What's happen ?

     

    Hsieh


  • 2.  Re: EGL debugging problem

    Posted Tue March 22, 2016 08:57 AM

    Hsieh,

    It sounds like it is trying to call a generated program rather than debug the called program.   Go into the "Preferences->EGL->Debug->Debug Behavior Mapping" and for that program make sure it is set to use "source", not generated.   Normally you are prompted for which to use and it remembers it.  So maybe this was accidentally done the first time.

     

    The other issue could be that it "can't find" the program and so it thinks it should be calling generated code.   This does not sound like it should be the case, but if the debug behavior mapping is not an issue, then maybe you can try a "project->Clean->All projects" and try again.

     

    Mark

    markevans


  • 3.  Re: EGL debugging problem

    Posted Tue March 22, 2016 11:25 AM

    Mark,

    The package of called program in workspace was inconsistent.


    I did run project clean but didn't fix.  And I tried add the called programa BA001A in debug behavior mapping and very strange the BA001A is not in Called Target list.

    after programa BA001A package delete from Project and add into Project then the problema was fixed, The program BA001A is in Called Target list.

    But there is no need to add the programa BA001A in debug behavior mapping.

     

    It works now.

     

    Thanks !  Mark.

    Hsieh