Possible debugger issue.

Question

I am trying to debug a third party package which fails in the debugger but runs OK.
There are two issues.
1 It includes the following code in the package body (ie as package initialisation).
    gv_audit_dir := TRIM(pk_dbgen.GET_SYSTEM_PARAMETER(pmi_systemparameter_in => pk_parms_global.gi_drive_path))
                 || TRIM(pk_dbgen.GET_SYSTEM_PARAMETER(pmi_systemparameter_in => 20));
    dbms_output.put_line('AUDIT_DIR='||gv_audit_dir);
    IF LENGTH(gv_audit_dir) < 4 THEN
      gv_audit_dir := NULL;
    END IF;When this code is stepped through in the debugger, the 'if LENGTH(gv_audit_dir) < 4' condition is always true, regardless of the actual content of the variable. If I step over it seems to execute OK.
2. The procedure I am calling fails with primary key violations if run in the debugger, but works if run normally. It is doing too much for me to pin down where the failure is at the moment, but I'll try to simplify and reproduce.
Has anyone seen this kind of behaviour in the debugger.
SQLDeveloper 1557
RDBMS 9.2.0.7

Answer 1

After two days of trying I somehow managed to revive my iPod. First, I re-partitioned for PC. Next, I reformatted for DOS and zeroed all data. Just for kicks I repeated the process for OSX extended. Finally, I ran Restore. It restored very quickly. I still wasn't convinced so I Restored several more times. This time when I updated my iTunes library to the iPod it transferred very quickly and without any apparent pauses.