Toad World® Forums

Re: Re: Fwd: Toad Debugger Breaking

Okay – this was an annoyance but not big enough for me to find out who owns the
licensing info and work it through my organization.

I just retested this in Toad 10.6. What I now see is that when I try to step
over a procedure that includes an exception, the debugger jumps to the exception
handler of the called procedure where what I would prefer is that if the
exception is handled, it be ignored.

Here’s how I have my debugger options configured:

Here’s my test case where what I do is run break_control with a break set at
‘Before call’ and then a step over of the “break_test” call.

CREATE OR REPLACE PACKAGE GMNA_BASELINE_POC1.rg_test_break
IS
PROCEDURE break_test;

PROCEDURE break_control;
END rg_test_break;
/
CREATE OR REPLACE PACKAGE BODY rg_test_break
IS
PROCEDURE break_test
IS
v_chr VARCHAR2 (10);
BEGIN
v_chr := ‘Hello’;

  SELECT dummy
    INTO v_chr
    FROM DUAL
   WHERE 1 = 2;

EXCEPTION
WHEN OTHERS
THEN
DBMS_OUTPUT.put_line (‘In Exception’);

     NULL;

END break_test;

PROCEDURE break_control
IS
BEGIN
DBMS_OUTPUT.put_line (‘Before call’);

  break_test;

  DBMS_OUTPUT.put_line ('After call');

END break_control;
END rg_test_break;
/

On Mon, May 2, 2011 at 1:00 PM, Jeff Smith wrote:

You might want to open a support case with Quest. This board is informal, so
to expect an answer to every question from a Quest person is a little
unreasonable.

 

If you can provide the test case again, I’d be happy to try your scenario
in v10.6 and v11 – assuming it’s a Toad issue and not an Oracle one.

I see that the snapshot of the debugger settings didn’t make it into the
e-mail. Key is that I do not have the “Break on exceptions” item
within the debugger options window checked.

Also, I should have mentioned that I am running this against a 10.2 database.

On Mon, May 2, 2011 at 1:30 PM, Rumpi Gravenstein wrote:

Okay -- this was an annoyance but not big enough for me to find out who owns
the licensing info and work it through my organization.

I just retested this in Toad 10.6.  What I now see is that when I try to
step over a procedure that includes an exception, the debugger jumps to the
exception handler of the called procedure where what I would prefer is that
if the exception is handled, it be ignored.

Here's how I have my debugger options configured:

Here’s my test case where what I do is run break_control with a break
set at ‘Before call’ and then a step over of the
“break_test” call.

CREATE OR REPLACE PACKAGE GMNA_BASELINE_POC1.rg_test_break
IS
   PROCEDURE break_test;

   PROCEDURE break_control;

END rg_test_break;
/
CREATE OR REPLACE PACKAGE BODY rg_test_break
IS

   PROCEDURE break_test
   IS
      v_chr   VARCHAR2 (10);
   BEGIN
      v_chr := 'Hello';

      SELECT dummy
        INTO v_chr
        FROM DUAL
       WHERE 1 = 2;
   EXCEPTION
      WHEN OTHERS
      THEN
         DBMS_OUTPUT.put_line ('In Exception');

         NULL;
   END break_test;

   PROCEDURE break_control
   IS
   BEGIN
      DBMS_OUTPUT.put_line ('Before call');

      break_test;

      DBMS_OUTPUT.put_line ('After call');

END break_control;
END rg_test_break;
/

On Mon, May 2, 2011 at 1:00 PM, Jeff Smith wrote:

    You might want to open a support case with Quest. This board is
    informal, so to expect an answer to every question from a Quest person
    is a little unreasonable.

     

    If you can provide the test case again, I’d be happy to try your
    scenario in v10.6 and v11 – assuming it’s a Toad issue and not an
    Oracle one.

I tried it both ways, on – it breaks on exception.

Off, it does not break on exception.

Are you able to test on a 11g database, or can you upgrade to v10.6?

Do you still have Toad 9.7 laying around? Curious if it still works there…

Jeff

Ahhh, my example was much simpler. I am not stepping over external calls that
have exceptions, I was simply stepping through an object that has an exception.

You can open your own support case with Quest, just use the information in Help

Licensing. Individual users can setup their own accounts at support.quest.com

Unfortunately I no longer have access to Toad 9.7 and don’t have access to
11g.

On Mon, May 2, 2011 at 1:36 PM, Jeff Smith wrote:

I tried it both ways, on – it breaks on exception.

 

Off, it does not break on exception.

 

Are you able to test on a 11g database, or can you upgrade to v10.6?

 

Do you still have Toad 9.7 laying around? Curious if it still works there…



Jeff

Done – Case ID: 915290

On Mon, May 2, 2011 at 1:40 PM, Jeff Smith wrote:

Ahhh, my example was much simpler. I am not stepping over external calls
that have exceptions, I was simply stepping through an object that has an
exception.

 

You can open your own support case with Quest, just use the information in
Help > Licensing. Individual users can setup their own accounts at
support.quest.com