<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Classic Debugger limitations - Explanation requested in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/classic-debugger-limitations-explanation-requested/m-p/7153338#M1514907</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'd really appreciate if one can explain me (in its true sense) what is meant by the following statements:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the classic debugger it is generally not possible to analyze prgrams in debugging mode that run in ABAP processor unit and are called recursively from subordinate unit. For example, a conversion exit cannot be analyzed using this debugger if it runs within a WRITE statement - The debugger in this case is called recursively from within itself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not able to understand what is meant by subordinate unit here and also how can I reproduce this in the system. Meaning what statements should I execute in the system to see it happening before my eyes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot!&lt;/P&gt;&lt;P&gt;Amiya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 09 Aug 2010 06:08:16 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2010-08-09T06:08:16Z</dc:date>
    <item>
      <title>Classic Debugger limitations - Explanation requested</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/classic-debugger-limitations-explanation-requested/m-p/7153338#M1514907</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'd really appreciate if one can explain me (in its true sense) what is meant by the following statements:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the classic debugger it is generally not possible to analyze prgrams in debugging mode that run in ABAP processor unit and are called recursively from subordinate unit. For example, a conversion exit cannot be analyzed using this debugger if it runs within a WRITE statement - The debugger in this case is called recursively from within itself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not able to understand what is meant by subordinate unit here and also how can I reproduce this in the system. Meaning what statements should I execute in the system to see it happening before my eyes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot!&lt;/P&gt;&lt;P&gt;Amiya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Aug 2010 06:08:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/classic-debugger-limitations-explanation-requested/m-p/7153338#M1514907</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-08-09T06:08:16Z</dc:date>
    </item>
    <item>
      <title>Re: Classic Debugger limitations - Explanation requested</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/classic-debugger-limitations-explanation-requested/m-p/7153339#M1514908</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; Hello Experts,&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; I'd really appreciate if one can explain me (in its true sense) what is meant by the following statements:&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; With the classic debugger it is generally not possible to analyze prgrams in debugging mode that run in ABAP processor unit and are called recursively from subordinate unit. For example, a conversion exit cannot be analyzed using this debugger if it runs within a WRITE statement - The debugger in this case is called recursively from within itself.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; I am not able to understand what is meant by subordinate unit here and also how can I reproduce this in the system. Meaning what statements should I execute in the system to see it happening before my eyes.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; Thanks a lot!&lt;/P&gt;&lt;P&gt;&amp;gt; Amiya&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;REPORT  zytest1.
DATA:
  w_matnr TYPE matnr VALUE '1234'.

WRITE : w_matnr.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Place a break point at the WRITE statement, debug the code(F5) in both classic and new debuggers and the see the difference for yourself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Rajesh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Aug 2010 09:38:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/classic-debugger-limitations-explanation-requested/m-p/7153339#M1514908</guid>
      <dc:creator>rajesh_paruchuru</dc:creator>
      <dc:date>2010-08-09T09:38:57Z</dc:date>
    </item>
    <item>
      <title>Re: Classic Debugger limitations - Explanation requested</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/classic-debugger-limitations-explanation-requested/m-p/7153340#M1514909</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Rajesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That was wonderful! Thanks a lot. I was able to see the difference and generate exception RPERF_ILLEGAL_STATEMENT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have more questions. Why the followingpiece of code doesn't work like yours. I was trying that piece of code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;DATA v_general TYPE num10 VALUE '0000154633'.
WRITE v_general USING EDIT MASK '==ALPHA'.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; ..and does the subordinate unit mean the 'Kernel' here?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for you response!&lt;/P&gt;&lt;P&gt;Amiya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Aug 2010 15:25:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/classic-debugger-limitations-explanation-requested/m-p/7153340#M1514909</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-08-09T15:25:30Z</dc:date>
    </item>
  </channel>
</rss>

